➜

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, BreamoreBoy, asvetlov, bjornedstrom, christian.heimes, dstufft, englabenny, ezio.melotti, gregory.p.smith, haakon, habnabit, jcea, larry, markk, pitrou, python-dev, sbt, tim.peters
Date 2013-11-01.18:08:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1383329303.39.0.254175564052.issue16113@psf.upfronthosting.co.za>
In-reply-to
Content 
New information on NIST's hash forum strongly suggest that NIST is going to standardize SHA-3 according to the original proposal with c=2n and Sakura padding as well as two SHAKEs with variable length output.

SHA3-224 with c=448
SHA3-256 with c=512
SHA3-384 with c=768
SHA3-512 with c=1024

SHAKE128 with c=256
SHAKE256 with c=512
History
Date User Action Args
2013-11-01 18:08:23christian.heimessetrecipients: + christian.heimes, tim.peters, gregory.p.smith, jcea, pitrou, larry, habnabit, ezio.melotti, Arfrever, asvetlov, englabenny, BreamoreBoy, python-dev, sbt, bjornedstrom, dstufft, markk, haakon
2013-11-01 18:08:23christian.heimessetmessageid: <1383329303.39.0.254175564052.issue16113@psf.upfronthosting.co.za>
2013-11-01 18:08:23christian.heimeslinkissue16113 messages
2013-11-01 18:08:23christian.heimescreate