FTP Session 8 127.0.0.1 TLS Handshake successful FTP Session 8 127.0.0.1 tls_layer_impl::continue_handshake() FTP Session 8 127.0.0.1 tls_layer_impl::server_handshake() FTP Session 8 127.0.0.1 234 Using authentication type TLS. FTP Session 8 127.0.0.1 220 Welcome to xxxxxxxx FileZilla Server So: is there a setting that I am missing in FluentFTP to overcome this error? Falling back to a single connection is a viable workaround, but since it is faster to use multiple connections it would be nice to find a better way forward. I know that I can turn off TLS session resumption in the FTP server - but I don't want to as it is there to help make the server more secure. I gather that TLS session resumption acts to prevent a hacker from connecting to the data port before the client does - if the TLS session of the data connection matches the session of the control connection then both the client and server know that the data connection is genuine, whereas a mismatch indicates a potential attack. I think (and this is pushing the bounds of my knowledge) that the message on the server indicates that the client does not support TLS session resumption. (036840) 10:55:19 - brian (10.0.0.26)> 450 TLS session of data connection has not resumed or the session does not match the control connection On the FTP server (FileZilla Server 0.9.60) I'm seeing this: Again, works very nicely using a single thread, but as soon as I start using 2 threads (so 2 simultaneous connections) I'm getting an IOException:Īuthentication failed because the remote party has closed the transport stream. I've recently done some work on extending this to work with FTPS. (Great library by the way.) My application is multi-threaded, with each thread having its own instance of FtpClient but with the same ftp credentials, all connecting to the same FTP server just doing different file-copy or directory listing tasks.
0 Comments
Leave a Reply. |