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, englabenny, ezio.melotti, gregory.p.smith, habnabit, jcea, maker, pitrou, python-dev, sbt
Date 2013-06-27.10:32:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Hi Aaron,

it's a tempting idea but I have to decline. The API is deliberately limited to the NIST interface. Once OpenSSL gains SHA-3 support we are going to use it in favor for the reference implementation. I don't expect OpenSSL to provide the full sponge API.

I also like to keep all options open so I can switch to a different and perhaps smaller implementation in the future. The reference implementation is huge and the binary is more than 400 KB. For comparison the SHA-2 384 + 512 module's binary is just about 60 KB on a 64bit Linux system.

Once a a new API has been introduced it's going to take at least two minor Python release and about four to five years to remove it.

But I could add a more flexible interface to Keccak's sponge to my standalone sha3 module ...
Date User Action Args
2013-06-27 10:32:07christian.heimessetrecipients: + christian.heimes, gregory.p.smith, jcea, pitrou, habnabit, ezio.melotti, Arfrever, asvetlov, englabenny, maker, python-dev, sbt, bjornedstrom
2013-06-27 10:32:07christian.heimessetmessageid: <>
2013-06-27 10:32:07christian.heimeslinkissue16113 messages
2013-06-27 10:32:07christian.heimescreate