Subject: bin/8173: FTPD inaccurate support of LIST command with path argument
To: None <>
From: None <>
List: netbsd-bugs
Date: 08/07/1999 23:50:55
>Number:         8173
>Category:       bin
>Synopsis:       FTPD inaccurate support of LIST command with path argument
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Aug  7 23:50:01 1999
>Originator:     Will Fong
>Release:        1.4/SPARC NetBSD Release
NetBSD 1.4 NetBSD 1.4 (SEEL) #0: Sat Aug  7 20:15:35 PDT 1999 sparc

Under FTP RFC-959, the LIST command is suppose to be take an argument that represents a path for the LIST command
to basically run the equivalent of an "ls -la" against.  When the argument has spaces in it, it fails horribily.

Under NetBSD 1.3I, you could run LIST "path" as long as the "path" did not have spaces in it.  If it did, it would fail to find the directory.
  - try "LIST a 1" or LIST "a 1/2", where "a 1" and "2" are directory names.

Under NetBSD 1.4, running "LIST 1/2/3" where "1","2" and "3" are directory names gives you the correct result.
Using "LIST a 1", where "a 1" is a directory name also works fine.
However, if you ask it to "LIST a 1/2/3" where "a 1" is the directory name, or "LIST 1/a 2/3", FTPD spits out nothing
to the data port.
In summary, under 1.4, running LIST with a path, where the path has both a subdirectory slash "/" and a space " ", the LIST command returns nothing.

The best way to see this for yourself is do the following:
telnet localhost 21 (where localhost is the computer with 1.4)
user anonymous
(open second telnet session to port indicated)
then run the LIST command as described above.

no known fix, but if anyone can confirm and make some progess on this, it would be appreciated if you got back to me via email.