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 r.david.murray
Recipients christian.heimes, pitrou, r.david.murray, vstinner
Date 2014-03-13.17:56:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394733387.87.0.332479882256.issue20913@psf.upfronthosting.co.za>
In-reply-to
Content
It's great that Christian did all the work he did on the SSL module to enhance its security capabilities, and great that Antoine did the work he did before that.  Now we need an explanation of how best to use it all :)


It is not clear from the existing documentation how to best use the various standard library modules that support SSL in a "best practices" way.  Perhaps this could go in the SSL docs and be linked from all the library components that use it.  Alternatively we could perhaps have a general security overview chapter in the library reference, but we at least an SSL one.  The existing documentation in the SSL module, while it contains a lot of information about the available, doesn't make it clear what a programmer should actually *do*.  As one example, it is not clear when or even if an application programmer would call check_hostname.
History
Date User Action Args
2014-03-13 17:56:27r.david.murraysetrecipients: + r.david.murray, pitrou, vstinner, christian.heimes
2014-03-13 17:56:27r.david.murraysetmessageid: <1394733387.87.0.332479882256.issue20913@psf.upfronthosting.co.za>
2014-03-13 17:56:27r.david.murraylinkissue20913 messages
2014-03-13 17:56:27r.david.murraycreate