>>>> "jam" == John A Martin
>>>> "Re: rssh.el interactions with ange-ftp/efs "
>>>> Sat, 16 Jan 1999 11:10:27 -0500
>>>> "Sandy" == Sandy Rutherford
>>>> "Re: rssh.el interactions with ange-ftp/efs"
>>>> Sat, 16 Jan 1999 02:16:14 -0800 (PST)
Sandy> BTW, does anybody out there know of other file transfer
Sandy> servers (other than FTP) that follow a tight protocol spec?
Sandy> If so, than EFS support for it might be possible.
jam> Long overdue on my to do list is to look at
jam> <
http://www.docs.uu.se/~pem/hacks/ftpsshd-1.1.tar.gz>. That
jam> reportedly works with ssh-1.2.26 atop Solaris or Linux at
jam> least. IIRC it talks to a standard ftpd but through
jam> redirected ssh secured channels.
A quick look indicates that ftpsshd works as advertised on linux when
built with gcc-2.7.2.1 and libc5 with slight obvious adjustments.
Normal remote ftp server and local ftp clients are used with both
control and data channels redirected through ssh encrypted (and
optionally compressed) connections. I found both the ftp client from
NetKit-B-0.09 and ncftp-1.9.9e to work for me with no surprises when
talking through ftpsshd to a wu-2.4.2-academ[BETA-18] ftp server.
ftpsshd is GPLed and might be a candidate to let efs do ssh-1.2.26
secured ftp. ftpsshd itself contains no crypto. A little work would
be needed to make ftpsshd portable wherever ssh-1.2.x goes; but it is
small, the sources total less than 1,300 lines including comments.
Perhaps a portable ftpsshd.el would be doable? Or using the
four-letter-p-word?
jam