GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||
GeezerVison is showing github.com — bpo-44888: Add ssl.OP_LEGACY_SERVER_CONNECT by xtkoba · Pull Request #27776 · python/cpython Conversation
|
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
See also openssl/openssl#16278 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Please add a NEWS entry. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Please also add documentation update and a test case. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I have made the requested changes; please review again. Note that the connection test would really require an "unpatched" server, which I didn't come up with how to prepare. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks for making the requested changes! @tiran: please review the changes made to this pull request. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Hi @xtkoba , just checking is this ssl.OP_LEGACY_SERVER_CONNECT issue already fixed in Python OpenSSL 3.0.0 side? Source of Issue: https://bugs.python.org/issue44888 I've tried with configure with ssl.OP_LEGACY_SERVER_CONNECT in OpenSSL 3.0.0, but can't found this option as per error messages below: Checked also in Python OpenSSL 3.0.0 documentation (Link: https://docs.python.org/3/library/ssl.html), also can't found this option. In this situation, what is best workaround solution for making OpenSSL 3.0.0 behave like 1.1.1 due to unable configure ssl.OP_LEGACY_SERVER_CONNECT as of now? Thanks. CC: @tiran |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
The changeset has not been merged and the flag is not available. @xtkoba closed the PR. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Note to self/others, I was able to work around by manually setting the numeric value. ctx = ssl.create_default_context(ssl.Purpose.SERVER_AUTH) ctx.options |= 0x4 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.