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 madison.may
Recipients christian.heimes, daniel.urban, debatem1, devin, dmalcolm, eric.araujo, exarkun, georg.brandl, giampaolo.rodola, gregory.p.smith, heikki, jsamuel, lemburg, loewis, lorph, madison.may, mcepl, mcrute, ncoghlan, pitrou, vstinner
Date 2013-08-02.21:42:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375479779.99.0.778346245122.issue8998@psf.upfronthosting.co.za>
In-reply-to
Content
This issue may have been dead for 3+ years, but perhaps it's time its brought back to the surface.  Aside from simple being convenient for general security practices, a stdlib module for crypto routines would enable python to handle encrypted zipfiles and resolve issues like issue9170. Currently, only hashlib and hmac are available to users (see http://docs.python.org/3/library/crypto.html).  

I'd imagine that collaboration with the likes of Dwayne from PyCrypto or further collaboration with Geremy from Evpy would be possible, and perhaps the stdlib could build on a 3rd party crypto library.  Is anyone else interested in working to make this happen (or does anyone have a good argument against a stdlib crypto library)?  I imagine it would be difficult to maintain, but perhaps its at least worth giving this issue a second chance.
History
Date User Action Args
2013-08-02 21:43:00madison.maysetrecipients: + madison.may, lemburg, loewis, georg.brandl, gregory.p.smith, exarkun, ncoghlan, pitrou, vstinner, giampaolo.rodola, christian.heimes, lorph, heikki, mcepl, eric.araujo, debatem1, dmalcolm, daniel.urban, mcrute, jsamuel, devin
2013-08-02 21:42:59madison.maysetmessageid: <1375479779.99.0.778346245122.issue8998@psf.upfronthosting.co.za>
2013-08-02 21:42:59madison.maylinkissue8998 messages
2013-08-02 21:42:59madison.maycreate