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 pitrou
Recipients llaniscudani, loewis, pitrou
Date 2012-06-17.21:04:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1339967070.76.0.602679058949.issue15071@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, so it seems the functionality is described in http://tools.ietf.org/html/rfc5705. If I understand correctly, it takes an ASCII label string, an optional context bytestring, and the length of the desired derived key. It then returns a bytestring of the given length, shared between client and server.

The low-level implementation of the ssl module is in Modules/_ssl.c. We probably want to add a method to PySSLSocket_Type there. Then in Lib/ssl.py there'll have to be a SSLSocket method to call the former method.

Tests should go in Lib/test/test_ssl.py.
History
Date User Action Args
2012-06-17 21:04:31pitrousetrecipients: + pitrou, loewis, llaniscudani
2012-06-17 21:04:30pitrousetmessageid: <1339967070.76.0.602679058949.issue15071@psf.upfronthosting.co.za>
2012-06-17 21:04:29pitroulinkissue15071 messages
2012-06-17 21:04:28pitroucreate