This module implements Keccak-f1600 sponge permutation and high-level APIs for various modes of it, including SHA-3 hashes.
This implementation is up-to-date with final version of FIPS-202 (5-Aug-2015).
Features:
Hashing (SHA3), PRNG, Stream cipher, AEAD cipher (SpongeWrap).
Optimized-C implementation from Keccak reference code, with separate paths for 64- and 32-bit CPUs.
Works with both Python 2.x and 3.x.
Todo:
Optimized ASM implementations.
Other Keccak permutation sizes.
Other sponge algorithms.
Other sponge modes.
Example:
from spongheshaker.sha3 import sha3_256, shake128
# fixed-length output
md = sha3_256('Hello ')
md.update('world!')
hash = md.digest()
# variable-length output
md = shake128('Hello ')
md.update('world!')
res1 = md.extract(64)
res2 = md.extract(64)
Links:
Git repo
1 maintainer
Metadata
1 maintainer
Release files for spongeshaker 1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| spongeshaker-1.3.tar.gz | 27.7 kB | Without provenance | Details |
Release files / spongeshaker-1.3.tar.gz
| Download URL | spongeshaker-1.3.tar.gz |
|---|---|
| Size | 27.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
03a2faf645fc0f000a0d785a31704d2905ee4eb45200107e931512173271c224
|
|
BLAKE2b-256 checksum How to use checksums |
58a9e42ee338acb4f5fe8eb8e7d94ae98a9935a1e97e20812300d0f852cd1f99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for spongeshaker 1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
