bpo-44888: Add ssl.OP_LEGACY_SERVER_CONNECT#27776
bpo-44888: Add ssl.OP_LEGACY_SERVER_CONNECT#27776xtkoba wants to merge 7 commits intopython:mainfrom
Conversation
Required for making OpenSSL 3.0.0 behave like 1.1.1.
|
See also openssl/openssl#16278 |
|
Please add a NEWS entry. |
|
Please also add documentation update and a test case. |
|
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 |
|
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. |
|
Thanks for making the requested changes! @tiran: please review the changes made to this pull request. |
|
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 |
|
The changeset has not been merged and the flag is not available. @xtkoba closed the PR. |

Required for making OpenSSL 3.0.0 behave like 1.1.1.
https://bugs.python.org/issue44888