-
Notifications
You must be signed in to change notification settings - Fork 409
FTP TLS session resumption not supported. #1617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
can you specify "do not work"? Do you see a specific error message. KP2A is using FluentFTP, I would neet to search for how to resolve this there. |
Seems this is a limitation in FluentFTP and their reliance on .NET Basily with this limitation, FTPS is insecure. And i'm going to guess using a different FTP backend is not an available option. |
Isn't a new session each time, more secure than reuse? I understand the performance benefits from TLS handshaking. |
As far as FTP goes, it doesn't. See, FTP Data channel is not authenticated, so any attacker could connect to this Data port and get access to information. As only the communication via port 21 is authenticated, it is a good idea to use that token for the Data channel as well. |
I continue to encounter this problem also with open-source FileZilla Server, latest v1.5.1 (min TLS 1.2) Below are 3 verbose log capture. 1st from Keepass2Android on local Wi-Fi, 2nd out/back through Internet, 3rd FileZilla Client, which connects fine either way. The former on DB selection displays "Warning: Server certificate validation failed: RemoteCertificateChainErrors. Install appropriate root certificate on your device or see settings." - despite Applicable Hostnames on Self-Signed cert including local server IP "pinkduck.myddns.me 192.168.1.71". Keepass2Android log (Android 10 to FileZilla Server 1.5.1, both on local Wi-Fi network) and Keepass2Android log (Android 10 to FileZilla Server 1.5.1 via cellular network, FZ server open to *) FileZilla Client’s detailed successful connection log: |
Just some related news:
|
FileZilla Server updated to GnuTLS 3.8.0 in v1.6.7 (released 20th Feb 2023), so I'll give that a try shortly to see if it resolves. |
Unfortunately not: <29-04-2023 10:32:37> FTP Session 3 192.168.1.164 Pink Duck [Response] 150 Starting data transfer. |
@PinkDuck , my point actually was that (theoretically) it should be easy to patch keepass2android ( I'm not saying there are no caveats possible, though. |
@PhilippC , sorry for bumping, but could you please look into this?
AFAIU, newest FluentFTP versions make it fairly easy to use the "GnuTLS" version that got this fixed (and they do recommend it regularly: 773 ). |
I tried to use GnuTLS, but failed. I created robinrodricks/FluentFTP#1736. https://github.com/PhilippC/keepass2android/tree/1617-use-gnu-tls-stream |
Using keepass2android with FTPS (FTP over or with TLS) servers that require TLS session resumption do not work.
This is mainly a security feature and partially a minor performance boost in connection setup.
Any chance this could be added?
The text was updated successfully, but these errors were encountered: