-
Notifications
You must be signed in to change notification settings - Fork 188
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
Runtime error with OpenSSL 1.1.0f and mod_sftp (was ok with OpenSSL 1.0.1f) #547
Comments
Just tested with 1.3.6 and it seems to be ok. Not sure 1.3.6 is production ready however... |
I cannot use v1.3.6 for now due to Castaglia/proftpd-mod_rename#4 |
Thanks for the fix for mod_rename and for your responsiveness, I really appreciate that 👍 working version:
Non working version:
There might be other differences between the 2 systems but this is the only one I've spotted |
I am thinking that you are encountering Bug#4240; the OpenSSL 1.1.x API changed -- and ProFTPD 1.3.5 does not have the corresponding code changes for that newer OpenSSL version. You can see for yourself what changes may be needed:
With the release of ProFTPD 1.3.6 stable, though, there will not be any backported changes to the 1.3.5 branch; see the Versioning doc. |
Fair enough about the versioning model but in that case, that really seems to be a critical bug as the application is just completely unusable. At least a warning about that should be added in the doc maybe... I'm testing v.1.3.6 and will upgrade if everything is ok. |
Happy to close this issue as 1.3.6 is working with last version of openssl and the FAQ has been updated for previous version < 1.3.6 |
Great, will do. Thanks! |
What I Did
Trying to connect with a simple command line:
sftp -vvv -o PasswordAuthentication=yes -P 2222 example@127.0.0.1
Get disconnected on the client side:
Strace output:
On the server side:
What I Expected/Wanted
Be able to login :-)
ProFTPD Version and Configuration
Proftpd version (tried with 1.3.5d and 1.3.5e too)
Conf file:
The same setup is definitely working with OpenSSL 1.0.1f
The text was updated successfully, but these errors were encountered: