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
gh-89051: Add ssl.OP_LEGACY_SERVER_CONNECT #93927
Conversation
be10f55
to
364d875
Compare
def test_legacy_server_connect(self): | ||
client_context, server_context, hostname = testing_context() | ||
client_context.options |= ssl.OP_LEGACY_SERVER_CONNECT | ||
server_params_test(client_context, server_context, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a mechanism for creating a bad TLS server that doesn't support secure renegotiation indication?
@tiran can I get a review on this please? |
I guess you never found a why to create a server that does not support secure negotiations. Let's land this now anyway. |
I had a look into doing it with tlslite-ng or using openssl's or even just hand writing TLS down a plain socket.socket but it would add hundreds or thousands of lines to the PR I did raise a ticket with badssl chromium/badssl.com#507 if they implement it I'd be interested in integrating badssl.test as a docker container in the CPython CI. |
(I'm working my way through some PRs which have been approved and are labeled "awaiting merge", hence my seemingly bolt from the blue comment. Why? Read here.) This has been idle since early August. @graingert Is there reason to assume a buggy TLS implementation is in the works against which this can be tested? If not, perhaps it's time to merge and close? |
Yeah I think this just needs a merge |
Hi, any indication on when this will be merged & released ? |
Docs conflict resolved. |
@dmpe Merged now, will be in 3.12.0 alpha 4, scheduled for 2023-01-09 and if the backports land soon, will be in 3.10.10 and 3.11.2, both scheduled for 2023-02-06. |
Thanks @graingert for the PR, and @hugovk for merging it |
Sorry, @graingert and @hugovk, I could not cleanly backport this to |
Thanks @graingert for the PR, and @hugovk for merging it |
Sorry @graingert and @hugovk, I had trouble checking out the |
Thanks @graingert for the PR, and @hugovk for merging it |
Sorry, @graingert and @hugovk, I could not cleanly backport this to |
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com> Co-authored-by: Christian Heimes <christian@python.org> Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com> Fixes python#89051 (cherry picked from commit 79ccc03)
GH-100359 is a backport of this pull request to the 3.11 branch. |
GH-100360 is a backport of this pull request to the 3.10 branch. |
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com> Co-authored-by: Christian Heimes <christian@python.org> Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com> Fixes python#89051
I closed the backport PRs, as we don't normally backport new features to bugfix branches. https://devguide.python.org/versions/ This will be in the next 3.12.0 alpha 4, due on 2023-01-09. |
Fixes #89051