FS#25669 - [filezilla] GnuTLS error -12: A TLS fatal alert has been received

Attached to Project: Community Packages
Opened by Steven V (steabert) - Friday, 19 August 2011, 09:06 GMT
Last edited by Florian Pritz (bluewind) - Sunday, 25 September 2011, 10:41 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Florian Pritz (bluewind)
Jelle van der Waa (jelly)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description: after upgrading to filezilla 3.5.0-2 + gnutls 3.0.0-2, I can't connect to ny ftp server anymore, giving me the following message: "GnuTLS error -12: A TLS fatal alert has been received". After rolling back to filezilla 3.5.0-1 + gnutls 2.12.7-2, I can connect again.

Steps to reproduce:
upgrade to filezilla 3.5.0-2 + gnutls 3.0.0-2, open filezilla and connect to ftp server over port 990, requiring explicit FTP over TLS.
This task depends upon

Closed by  Florian Pritz (bluewind)
Sunday, 25 September 2011, 10:41 GMT
Reason for closing:  Fixed
Additional comments about closing:  filezilla 3.5.1-2
Comment by Florian Pritz (bluewind) - Friday, 19 August 2011, 12:13 GMT
It works fine with gnutls-cli so I think this is an upstream bug of filezilla.
Comment by WladyX (WladyX) - Monday, 29 August 2011, 17:05 GMT
I have the same issue, have you found a workaround, except downgrade/disable tls?
Thanks.
Comment by Tobias Hobmeier (F6F) - Saturday, 10 September 2011, 18:43 GMT
the problem is still present with filezilla 3.5.1 and gnutls-3.0.2-1
Comment by Florian Pritz (bluewind) - Saturday, 10 September 2011, 18:59 GMT
Please keep discussion about this bug upstream[1] unless you know for sure it's a packaging bug.

[1] http://trac.filezilla-project.org/ticket/7742
Comment by Sid Karunaratne (sakaru) - Sunday, 25 September 2011, 10:14 GMT
A patch[1] has been posted in the upstream ticket linked by Florian. I'm not sure the patch posted will be accepted as is, it does however work.

It is my opinion the patch should be incorporated into our PKGBUILD until the next version bump when this bug will likely be fixed without a patch. I know the Arch policy on patches, however in this case without it we lose substantial functionality. On the other hand, perhaps this is exactly when people should use the ABS.

[1] http://trac.filezilla-project.org/attachment/ticket/7742/patch.txt

Loading...