➜

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 Arfrever, asvetlov, bjornedstrom, christian.heimes, dstufft, englabenny, ezio.melotti, gregory.p.smith, haakon, habnabit, jcea, larry, loewis, markk, pitrou, python-dev, sbt, spatz, tim.peters, vstinner
Date 2016-05-08.10:49:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1462704542.5.0.230908553557.issue16113@psf.upfronthosting.co.za>
In-reply-to
Content 
Larry,
I'm with Gregory. There is no good reason to add SHA3 to Python 2.7. The SHA-2 family is still safe. Besides I'd rather add BLAKE2 to Python 2.7. It's much faster and more versatile than SHA3.

Antoine,
SHAKEs are XOF (extensible output function). NIST has standardized the XOFs but not yet approved them as replacement for other constructs. They are useful for signatures or as a simple stream cipher. The SHAKEs were low hanging fruits to implement, so I included them.
History
Date User Action Args
2016-05-08 10:49:02christian.heimessetrecipients: + christian.heimes, tim.peters, loewis, gregory.p.smith, jcea, pitrou, vstinner, larry, habnabit, ezio.melotti, spatz, Arfrever, asvetlov, englabenny, python-dev, sbt, bjornedstrom, dstufft, markk, haakon
2016-05-08 10:49:02christian.heimessetmessageid: <1462704542.5.0.230908553557.issue16113@psf.upfronthosting.co.za>
2016-05-08 10:49:02christian.heimeslinkissue16113 messages
2016-05-08 10:49:02christian.heimescreate