This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients christian.heimes, docs@python, eric.smith
Date 2015-06-03.14:09:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433340594.69.0.984249982862.issue24372@psf.upfronthosting.co.za>
In-reply-to
Content
DISCLAIMER:

I'm currently planning and researching two SSL related PEPs. One PEP is about SSLContext.

I like to standardize a minimal interface for SSL context object, so libraries can deal with any abitrary SSL implementation. With just one small addition and an SSLContext ABC, every library could then support stdlib ssl, PyOpenSSL, GnuTLS, NSS, PyQT/PySide QSslSocket and even non-standard sockets like NSPR PRFileDesc and QTcpSocket.

My idea only works with a SSL context object. So I'm interested that people use the new feature rather then the old ssl.wrap_socket() function. :)
History
Date User Action Args
2015-06-03 14:09:54christian.heimessetrecipients: + christian.heimes, eric.smith, docs@python
2015-06-03 14:09:54christian.heimessetmessageid: <1433340594.69.0.984249982862.issue24372@psf.upfronthosting.co.za>
2015-06-03 14:09:54christian.heimeslinkissue24372 messages
2015-06-03 14:09:54christian.heimescreate