[issue24516] SSL create_default_socket purpose insufficiently documented

Changes by Christian Heimes : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pyt

[issue24516] SSL create_default_socket purpose insufficiently documented

Changes by Christian Heimes : -- components: +SSL ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue24516] SSL create_default_socket purpose insufficiently documented

Changes by Christian Heimes : -- versions: +Python 3.6, Python 3.7 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue24516] SSL create_default_socket purpose insufficiently documented

Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue24516] SSL create_default_socket purpose insufficiently documented

Christian Heimes added the comment: Python uses serverAuth and clientAuth in the exact same meaning as EKU (extended key usage). In order to create X.509 cert for a web server, it should have EKU "SSL/TLS Web Server Authentication". On the other hand a client must validate the cert for a speci

[issue24516] SSL create_default_socket purpose insufficiently documented

New submission from Petr Messner: Please, is it possible to put more information about the purpose parameter to the documentation of ssl.create_default_context()? It's not obvious that SERVER_AUTH should be used for client sockets and not server sockets. It took me a while to discover this, wh