-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Update to newer OpenSSL? #58170
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
Where does Julia use openssh exactly? |
I think you're talking about openssl instead? |
Yes, d'oh, this is about OpenSSL. 3.5 is the new LTS. |
If v3.5 has already been designated to be the next LTS then it sounds more than reasonable to switch to that version. PS: your first post still refers to OpenSSH multiple times. |
Updating to 3.5 should also help Python interoperability quite a bit. PythonCall via CondaPkg now needs to hold back Conda OpenSSL versions to 3.0 to avoid segfaults like JuliaPy/PythonCall.jl#586 (comment). But since conda-forge doesn't stick to OpenSSL LTS versions the ecosystem has long moved on and we cannot use PythonCall with recent Python releases. |
OpenSSH 3.0 (which Julia currently uses) might be unsupported after September 2026 (see https://openssl-library.org/source/). Should we switch to OpenSSH 3.5, the next LTS version of OpenSSH which was recently released? According to the documentation these versions should be API/ABI compatible.
The text was updated successfully, but these errors were encountered: