-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
Update to OpenSSL 1.1.1k #87797
Comments
OpenSSL 1.1.1k contains fixes for two high severity CVEs https://www.openssl.org/news/vulnerabilities.html |
When do you expect there will be new macOS and Windows downloads available at https://www.python.org/downloads/ that use OpenSSL 1.1.1k? One of my projects is relying on these files and I wasn't sure the ETA here. |
Assume it'll be the next scheduled release (though I haven't looked at the details of the vulnerabilities yet, so we may decide that they're more urgent for CPython users). I'm starting the Windows build process now, but that only gets us far enough to do the integration, it's not a release. |
Thanks! My mail https://mail.python.org/archives/list/python-dev@python.org/thread/2GULUR43MNEW3IJM44LS5ZY2TOUANPNT/ contains a first analysis of the CVEs. I'm pretty sure any server application with server-side TLS socket is vulnerable to CVE-2021-3449. |
I published the Windows OpenSSL builds and retriggered your PR builds, Christian. It looks like we should probably bring up the next release for this, if only because that will cause server users to do rebuilds/updates that they may otherwise not. I doubt there are many public-facing servers running on Windows or macOS (most Windows ones let IIS handle TLS anyway, rather than doing it in Python), though Brad may be an exception here ;) |
Thanks! All tests are passing, but macOS is still using OpenSSL 1.1.1j. |
To be fair, I doubt my project is affected by the CVEs. I was just looking to upgrade instead of trying to verify that. |
CI, macOS and Windows infrastructure have been updated. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: