elisp-code-efs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Elisp-code-efs] Re: EFS 1.23 bug: EFS, lukemftp and hosts that don't su


From: Luke Mewburn
Subject: [Elisp-code-efs] Re: EFS 1.23 bug: EFS, lukemftp and hosts that don't support extended modes
Date: Wed, 11 Apr 2007 15:04:48 +1000
User-agent: Mutt/1.4.2.2i

On Wed, Mar 16, 2005 at 02:42:38PM +0100, Michael Sperber wrote:
  | >>>>> "Luke" == Luke Mewburn <address@hidden> writes:
  | 
  | Luke> On Wed, Mar 02, 2005 at 06:08:25PM +0100, Michael Sperber wrote:
  | Luke>   | Joachim> My ftp client is lukemftp, version 1.5.
  | Luke>   | 
  | Luke>   | Ah.  This is a mess.  The interaction with lukemftp looks like 
this:
  | Luke>   | 
  | Luke>   | ftp> ls
  | Luke>   | 500 Unknown command.
  | Luke>   | 227 Entering Passive Mode (129,128,5,190,169,64)
  | Luke>   | 
  | Luke>   | I dare say that "Unknown command" confuses not just EFS, but also
  | Luke>   | human users: since lukemftp issues a command secretly, it should 
also
  | Luke>   | eat the response.  I have no idea how to work around this, since 
500
  | Luke>   | may be a genuine error in a circumstance like this.  (The
  | Luke>   | Heimdal ftp client attempts extended passive, too, but discards 
the
  | Luke>   | 500 response, and thus works fine with EFS.)
  | Luke>   | 
  | Luke>   | Hi Luke, maybe this can be fixed in lukemftp?
  | 
  | Luke> Please try the latest version -- it has been renamed to tnftp -- which
  | Luke> can be found at:
  | Luke>       ftp://ftp.NetBSD.org/pub/NetBSD/misc/tnftp/tnftp-20050103.tar.gz
  | Luke> (PGP signature
  | Luke>       
ftp://ftp.NetBSD.org/pub/NetBSD/misc/tnftp/tnftp-20050103.tar.gz.asc
  | Luke> )
  | 
  | Thanks---unfortunately, that has the exact same problem.


I have fixed the code in the NetBSD ftp client for this, and
the fix will make it into the next public release of tnftp
(which is an autoconf-ed portable version of the NetBSD ftp client).


I hope that helps, and apologies for the long delay in resolving
this issue.


cheers,
Luke.

Attachment: pgpy5yWXbYPvd.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]