Annotation of 43BSDReno/libexec/ftpd/CHANGES, revision 1.1

1.1     ! root        1: This version of ftpd has been fixed to conform to RFC959.
        !             2: 
        !             3: Unfortunately, this conformance introduces a user visible change.  While
        !             4: technically, this is the fault of the client (ftp) instead of the server
        !             5: (ftpd), the change will be seen whenever an old ftp client calls a new ftpd
        !             6: server.
        !             7: 
        !             8: The problem is that the old ftpd implemented the NLST command by execing
        !             9: /bin/ls.  This produced non-conformant output in some cases.  The new
        !            10: ftpd no longer executes /bin/ls for the NLST command as it has it's own
        !            11: built-in code.
        !            12: 
        !            13: The user visible change in the ftp behavior is caused by the ftp client
        !            14: "knowing" that the daemon will exec /bin/ls.  This assumption should not
        !            15: have been made.
        !            16: 
        !            17: When the old ftp client is used, one of the options is the "ls" command
        !            18: which sends the command NLST to the ftpd server.  The client should really
        !            19: be sending the LIST command.  The new ftp client has been corrected to do
        !            20: this.
        !            21: 
        !            22: NLST should not normally be used directly by humans.  It is intended to
        !            23: interface with commands like mget or mput.
        !            24: 
        !            25: Users who are not able to upgrade their ftp client may obtain the previous
        !            26: behavior, by using the command "dir" instead of "ls".
        !            27: 
        !            28: These changes only apply to those sites using code derived from the Berkeley
        !            29: software releases (which means almost every UNIX based implementation will
        !            30: see this problem).
        !            31: 

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.