-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
Clean up some confusing text left by PROTOCOL_SSLv23 -> PROTOCOL_TLS transition #1355
Conversation
…transition It was confusing that PROTOCOL_SSLv23 could negotiate TLS connections. It is not confusing that PROTOCOL_TLS can negotiate TLS connections. In fact it is confusing that the docs thought it was confusing.
(This should have the "trivial" label, but I don't have permissions to add it.) |
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
SSLv23
is an artefact from the time when OpenSSL just had support for SSLv2 and SSLv3. It took me years do understand that PROTOCOL_SSLv23 actually means auto-negotiation of the highest protocol enabled on both sides.
…L_TLS transition (pythonGH-1355) (cherry picked from commit d4069de)
Sorry, @njsmith and @Mariatta, I could not cleanly backport this to |
It was confusing that PROTOCOL_SSLv23 could negotiate TLS connections. It is not confusing that PROTOCOL_TLS can negotiate TLS connections. In fact it is confusing that the docs thought it was confusing.