➜

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, loewis, markk, pitrou, python-dev, sbt, tim.peters, vstinner
Date 2014-01-02.20:52:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1388695943.76.0.64072773091.issue16113@psf.upfronthosting.co.za>
In-reply-to
Content 
I have created a backport of the sha3 for Python 2.6 to 3.3 about an year ago. It's on PyPI: https://pypi.python.org/pypi/pysha3 . I'm planing to update the code with SHAKE256 and SHAKE512 support soonish, too.

I have very high confidence that NIST is neither going to change the parameters or padding for SHA3 nor is NIST going to deviate from the original Keccak proposal. In case you still prefer to remove SHA3 I suggest that we stick to GPS' plan and wait until RC1.

The attached patch removes all code and documentation for SHA3.
History
Date User Action Args
2014-01-02 20:52:27christian.heimessetrecipients: + christian.heimes, tim.peters, loewis, gregory.p.smith, jcea, pitrou, vstinner, larry, habnabit, ezio.melotti, Arfrever, asvetlov, englabenny, BreamoreBoy, python-dev, sbt, bjornedstrom, dstufft, markk, haakon
2014-01-02 20:52:23christian.heimessetmessageid: <1388695943.76.0.64072773091.issue16113@psf.upfronthosting.co.za>
2014-01-02 20:52:23christian.heimeslinkissue16113 messages
2014-01-02 20:52:23christian.heimescreate