-
-
Notifications
You must be signed in to change notification settings - Fork 31k
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 3.0.13 (& 1.1.1w) in our binary release build process. #109991
Comments
I just pushed updated Windows builds of OpenSSL to the cpython-bin-deps for OpenSSL 1.1.1w and 3.0.11. |
(cherry picked from commit 884cd18)
…ssltests to use 1.1.1w, 3.0.11, and 3.1.3. (gh-110002)
… multissltests to use 1.1.1w, 3.0.11, and 3.1.3. (pythongh-110002) (cherry picked from commit c88037d) Co-authored-by: Ned Deily <nad@python.org>
… multissltests to use 1.1.1w, 3.0.11, and 3.1.3. (pythongh-110002) (cherry picked from commit c88037d)
… multissltests to use 1.1.1w, 3.0.11, and 3.1.3. (cherry picked from commit c88037d)
… multissltests to use 1.1.1w and 3.0.11. (cherry picked from commit c88037d)
… multissltests to use 1.1.1w and 3.0.11. (cherry picked from commit c88037d)
…nGH-110003) (cherry picked from commit 98c0c1d) Co-authored-by: Ned Deily <nad@python.org>
…nGH-115052) (cherry picked from commit 638e811) Co-authored-by: Ned Deily <nad@python.org>
…nGH-115052) (cherry picked from commit 638e811) Co-authored-by: Ned Deily <nad@python.org>
Also update multissltests to use 1.1.1w, 3.0.13, 3.1.5, and 3.2.1.
…ythonGH-115050) Also update multissltests to use 1.1.1w, 3.0.13, 3.1.5, and 3.2.1. (cherry picked from commit 299e16c) Co-authored-by: Ned Deily <nad@python.org>
Is there anything left to do before the next 3.12 release (scheduled for today)? |
I think we are good to go for 3.12 and 3.11. There could be backports needed for 3.10, 3.9, and 3.8 at the discretion of their release managers. |
The 3.8-3.10 Windows builds are still on 1.1.1w and would require a larger-than-usual backport to jump up to 3.0. I'm not sure it's worthwhile since we're no longer producing binaries for those versions. If we do decide to do that backport I think it's worth a new issue, so I'm closing this one. |
…ython#115050) Also update multissltests to use 1.1.1w, 3.0.13, 3.1.5, and 3.2.1.
… multissltests to use 1.1.1w, 3.0.11, and 3.1.3. (pythongh-110002)
Bug report
Bug description:
We need to upgrade the OpenSSL versions we build & bundle into our binary releases before the next release. More security fixes as usual. In particular https://nvd.nist.gov/vuln/detail/CVE-2023-4807 applies to our 64-bit Windows binaries.
Pick the latest 3.0.x and 1.1.1 releases at the time the work is done. 3.0.11 today, and if we build binaries for older shipping-with-1.1 branches, 1.1.1w. We should update the binary build tooling in older release branches for those to at least reference and pull in 1.1.1w even if we aren't shipping new binary releases on those ourselves.
CPython versions tested on:
3.8, 3.9, 3.10, 3.11, 3.12
Operating systems tested on:
macOS, Windows
Linked PRs
The text was updated successfully, but these errors were encountered: