David,
On 16 Jan 1999 you wrote:
I can log in as root with ssh, if I could do the eqivalent of the
above using ssh I'd be happier.
The problem with having EFS support sftp is that the ssh people
haven't implemented a proper FT protocol with return codes. For
example:
sftp> pwd
/home/sandy
as opposed to
ftp> pwd
257 "/home/sandy" is current directory.
EFS relies heavily (in fact almost exclusively) on the numeric codes
to determine the success of remote commands and the state of
the server. The meanings of these codes is defined in RFC 959 and I
wrote the EFS process filter as a strict implementation of this RFC.
In my opinion, if people want ssh support in EFS (and I think that a
more secure version of FTP would be good), then you should go after
the ssh people to make sftp follow RFC 959. Trying to make EFS work
with a file transfer server that doesn't follow a rigid protocol is in
my opinion a waste of time. The result would be so flakey as to not
be worth the trouble. The FT Protocol as defined in RFC 959 is very
well designed for robust server-client interaction and the ssh people
would do well to use it.
BTW, does anybody out there know of other file transfer servers (other
than FTP) that follow a tight protocol spec? If so, than EFS support
for it might be possible.
...Sandy