-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
bpo-39616: clarify SSLContext.check_hostname effect #18484
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
bpo-39616: clarify SSLContext.check_hostname effect #18484
Conversation
For reference this was removed as part of: 61d478c#diff-c49248c7181161e24048bec5e35ba953 Looks like the proper |
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.
LGTM with suggestion.
cc4a99a
to
917a5c4
Compare
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.
Could you please just remove "with :func:match_hostname
" and leave the rest of the text formatted as it is? This reduces the diff. It's ok when some of the lines don't expand to 80 chars.
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 |
This is exactly what I did initially, but was asked to re-flow it. Will re-unflow again now :P |
It doesn't actually affect whether match_hostname() is called (it never is in this context any longer), but whether hostname verification occurs in the first place.
917a5c4
to
77a8118
Compare
Done. |
Oh, sorry for the extra work. I prefer smaller diffs over slightly nicer formatted markup. It's a matter of personal taste. |
Thanks @scop for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9. |
It doesn't actually affect whether match_hostname() is called (it never is in this context any longer), but whether hostname verification occurs in the first place. (cherry picked from commit 9798cef) Co-authored-by: Ville Skyttä <[email protected]>
GH-25036 is a backport of this pull request to the 3.9 branch. |
It doesn't actually affect whether match_hostname() is called (it never is in this context any longer), but whether hostname verification occurs in the first place. (cherry picked from commit 9798cef) Co-authored-by: Ville Skyttä <[email protected]>
GH-25037 is a backport of this pull request to the 3.8 branch. |
It doesn't actually affect whether match_hostname() is called (it never is in this context any longer), but whether hostname verification occurs in the first place. (cherry picked from commit 9798cef) Co-authored-by: Ville Skyttä <[email protected]>
It doesn't actually affect whether match_hostname() is called (it never is in this context any longer), but whether hostname verification occurs in the first place. (cherry picked from commit 9798cef) Co-authored-by: Ville Skyttä <[email protected]>
It doesn't actually affect whether match_hostname() is called (it
never is in this context any longer), but whether hostname
verification occurs in the first place.
https://bugs.python.org/issue39616
Automerge-Triggered-By: GH:tiran