aboutsummaryrefslogtreecommitdiff
path: root/src/Package/Fetch/git.zig
diff options
context:
space:
mode:
authorFrank Denis <124872+jedisct1@users.noreply.github.com>2024-04-09 21:16:19 +0200
committerGitHub <noreply@github.com>2024-04-09 12:16:19 -0700
commit9d27f34d04154069e2c2c37af99f35a50ac4bd9e (patch)
tree90088c3a7395b3e534dc937c802f47b6940ceea7 /src/Package/Fetch/git.zig
parentac21ade667f0f42b8b1aec5831cbc99cbaed8565 (diff)
downloadzig-9d27f34d04154069e2c2c37af99f35a50ac4bd9e.tar.gz
zig-9d27f34d04154069e2c2c37af99f35a50ac4bd9e.zip
crypto.sha3: implement constructions from NIST SP 800-185 (#19533)
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-185.pdf This adds useful standard SHA3-based constructions from the NIST SP 800-185 document: - cSHAKE: similar to the SHAKE extensible hash function, but with the addition of a context parameter. - KMAC: SHAKE-based authentication / keyed XOF - TupleHash: unambiguous hashing of tuples These are required by recent protocols and specifications. They also offer properties that none of the currently available constructions in the stdlib offer, especially the ability to safely hash tuples. Other keyed hash functions/XOFs will fall back to using HMAC, which is suboptimal from a performance perspective, but fine from a security perspective.
Diffstat (limited to 'src/Package/Fetch/git.zig')
0 files changed, 0 insertions, 0 deletions