Minor bugs

[darkone]

First:

CPSV
500 'CPSV': Command not understood
Site to Site Transfer Failed! (Attempting normal method)
CPSV
227 Entering Passive Mode (192,168,1,1,132,42)
PORT 192,168,1,1,132,42
200 PORT command successful.
STOR u-nis62.zip
150 Opening BINARY mode data connection for u-nis62.zip.
RETR u-nis62.zip
150 Opening BINARY mode data connection for u-nis62.zip (85183132 bytes).
426 Connection closed: The parameter is incorrect.
Transfer Failed!
426 Data connection: Connection reset by peer.

<< Client doesn't call PROT - both servers are still using encryption.

2) Type very long command on raw command line.. send it to server, press up/down arrow to resend same command: ffxp vanishes.

[MxxCon]

Originally posted by dark0n3
2) Type very long command on raw command line.. send it to server, press up/down arrow to resend same command: ffxp vanishes. define "very long" :)

[darkone]

I think it was over 2000chars :)

[darkone]

Also seems like ffxp was calling SSL_accept() for datachannel too early:

[10:08:31] STOR arrwdth_01.wav
[10:08:31] Negotiating SSL/TLS session...
^^ Client hangs here
[10:09:19] 550 arrwdth_01.wav: The process cannot access the file because it is being used by another process.

[bigstar]

1) I'll look into this
2) I'll look into this too
3) Some ftp servers (raidenftpd and others) require SSL_accept() to be called before issuing STOR or RETR

Which FTP server were you testing with?

[darkone]

io. From ftp SSL draft:

PORT w,x,y,z,a,b -------------------------------------------->
<-------------------------------------------------------- 200
STOR file --------------------------------------------------->
socket()
bind()
<-------------------------------------------------------- 150
accept() <---------- connect()
TLSneg() <----------> TLSneg()
TLSwrite() ----------> TLSread()
TLSshutdown() -------> TLSshutdown()
close() ----------> close()
<-------------------------------------------------------- 226

Both accept and TLSnegotation should occur after 150 response has been sent to client. But I guess we can't blame you for supporting those servers :)

[bigstar]

yeah i'm aware of the SSL draft.. I don't know if raidenftpd ever changed their behavior, however there was one other that did this too.. cant recall the name though.