| 2008-10-26 18:27:47 |
aldebx |
description |
Binary package hint: proftpd
This came up as the result of FileZilla releasing a new version of their client that no longer worked with ProFTPd and other FTP servers due to an adjustment in how that client reacts to TLS/SSL session closes. If the client doesn't receive proper notification, it aborts the session (this is my understanding).
There has been some discussion over whether the client's interpretation and subsequent implementation of the RFC's is correct or not, but perhaps some discussion can be had here and perhaps ultimately a resolution. As it is now, FileZilla >= v3.1.0 can no longer connect to ProFTPd via TLS/SSL. |
Binary package hint: proftpd
This came up as the result of FileZilla releasing a new version of their client that no longer worked with ProFTPd and other FTP servers due to an adjustment in how that client reacts to TLS/SSL session closes. If the client doesn't receive proper notification, it aborts the session (this is my understanding).
There has been some discussion over whether the client's interpretation and subsequent implementation of the RFC's is correct or not, but perhaps some discussion can be had here and perhaps ultimately a resolution. As it is now, FileZilla >= v3.1.0 can no longer connect to ProFTPd via TLS/SSL.
The upstream bug report is available at http://bugs.proftpd.org/show_bug.cgi?id=3094
The bug has been fixed upstream in proftpd v1.3.2rc2 |
|
