Martin v. Löwis added the comment: 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 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16113> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
