8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
961b2b6
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Add server_hostname parameter maybe? At least create_connection has it, checking hostname match increases security.
server_hostname
create_connection
Sorry, something went wrong.
Yes, server_hostname should be added. Or perhaps a bunch of kwargs to allow passing arbitrary arguments to wrap_socket or wrap_bio.
kwargs
wrap_socket
wrap_bio
Sure, will add it.
Or perhaps a bunch of kwargs to allow passing arbitrary arguments to wrap_socket or wrap_bio.
We don't do that in loop.create_connection or in loop.create_server, we explicitly pass params there. Most of the stuff can be configured through the SSLContext anyways.
loop.create_connection
loop.create_server
SSLContext
Yeah... I guess that could be deferred to another PR. However, the ssl module may add some other parameters along the way, and it would be nicer to inherit them automatically. For example, Python 3.6 got the session parameter: https://docs.python.org/3/library/ssl.html#ssl.SSLContext.wrap_socket
ssl
session
Sure. Can you make a PR after this one lands?
Clarification: asyncio doesn't use ssl.wrap_socket since Python 3.5
ssl.wrap_socket
Yes, but it uses ssl.wrap_bio which accepts similar arguments.
ssl.wrap_bio