It is basically what was changed in 2.0.7 ssl code, modulo other changes we don't want in this SRU as they are not useful for fixing this bug.Ģ) TEST CASE: Install vsftpd and configure it with ssl (certificate, ssl_enable=yes), try connecting to it with a recent version of FileZilla (eg.

The person who fixed that bug in Fedora gave me their patch, which I applied. That means this bug potentially affects any standard-compliant client. Clients such as recent FileZilla which decided to enforce SSL connections to be properly closed (because it is otherwise a security risk) now do not work with vsftpd 2.0.6 and other broken FTP servers. It is a problem in the SSL connection shutdown code, which doesn't follow the standard.

This is bug is fixed in intrepid as it is fixed in vsftpd 2.0.7. Pleas rebuild new version of vsftpd in HardyHeronġ) Explanation, rationale, and everything. In release notice of vsftpd-2.0.7 vsftpd.

On filezilla forum forum.filezilla -project. Status: Server did not properly shut down TLS connectionīłąd:Ĝould not read from transfer socket: ECONNABORTED - Connection aborted

In FileZilla ftp Client when connecting to vsftpd 2.0.6 server with explicit TLS/SSL on HardyHeron:

Install filezilla fedora 27