Another problem with ftp-proxy

[Steven Schoch]

This one seems to be caused by a mis-behaving FTP client, in this case
ClickTracks.

But ftp-proxy looks like it's doing something wrong.  Here are a few
lines from the logfile:

Nov 15 16:05:01 freebsd ftp-proxy[27010]: client line buffer is "STRU F^M "
Nov 15 16:05:01 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:01 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:01 freebsd ftp-proxy[27010]: server line buffer is "200
Structure okay.^M "
Nov 15 16:05:01 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:01 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:01 freebsd ftp-proxy[27010]: client line buffer is "CWD  "
Nov 15 16:05:01 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:01 freebsd ftp-proxy[27010]: client line buffer is "^M "
Nov 15 16:05:01 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:03 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:03 freebsd ftp-proxy[27010]: server line buffer is "501
Syntax error in parameters.^M "
Nov 15 16:05:03 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:03 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:03 freebsd ftp-proxy[27010]: client line buffer is "PASV^M "
Nov 15 16:05:03 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:06 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:06 freebsd ftp-proxy[27010]: server line buffer is "500
Syntax error, command unrecognized.^M "
Nov 15 16:05:06 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:06 freebsd ftp-proxy[27010]: client is alive; server is alive
Nov 15 16:05:06 freebsd ftp-proxy[27010]: server line buffer is "227
Entering Passive Mode (209,197,97,252,208,116)^M "

Notice that most of the client line buffers end in ^M, which I assume
is a good clue that the next character is a newline, but the "CWD"
line seems to be split in two, which results in two responses from the
server: "501 Syntax error" and "500 Syntax error".  The client seems
to handle the first 501 error ok, but since the 500 error is still in
its buffer, it sees that as an error to the "PASV" command.

Anyone else seen this?

--
Steve