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 loewis
Recipients Arfrever, BreamoreBoy, asvetlov, bjornedstrom, christian.heimes, dstufft, englabenny, ezio.melotti, gregory.p.smith, haakon, habnabit, jcea, larry, loewis, markk, pitrou, python-dev, sbt, tim.peters, vstinner
Date 2014-01-02.22:07:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1388700455.26.0.471829717447.issue16113@psf.upfronthosting.co.za>
In-reply-to
Content
I just looked at the hash-forum archives (*)

http://cio.nist.gov/esd/emaildir/lists/hash-forum/msg02809.html

which says that they plan to publish the draft "soon after Christmas".
They also indicate how the padding open issue might get resolved (append 1111 for SHAKE, 1101 for the SHA-2 drop-ins). Not sure whether this is what Christian has already implemented.

(*) See http://crypto.stackexchange.com/questions/10645/are-nists-changes-to-keccak-sha-3-problematic for the password
History
Date User Action Args
2014-01-02 22:07:35loewissetrecipients: + loewis, tim.peters, gregory.p.smith, jcea, pitrou, vstinner, larry, christian.heimes, habnabit, ezio.melotti, Arfrever, asvetlov, englabenny, BreamoreBoy, python-dev, sbt, bjornedstrom, dstufft, markk, haakon
2014-01-02 22:07:35loewissetmessageid: <1388700455.26.0.471829717447.issue16113@psf.upfronthosting.co.za>
2014-01-02 22:07:35loewislinkissue16113 messages
2014-01-02 22:07:35loewiscreate