aboutsummaryrefslogtreecommitdiff
path: root/lib/std
diff options
context:
space:
mode:
authorFrank Denis <github@pureftpd.org>2020-10-04 10:19:30 +0200
committerAndrew Kelley <andrew@ziglang.org>2020-10-15 20:50:34 -0400
commitcb44f27104937682ffaa42ec133e56595e4f08d0 (patch)
tree04e29b53b10c4db6c4ea31985e333b92e4e0cdc1 /lib/std
parenta66449c1edbd14f66cb0a87316d16f26121af353 (diff)
downloadzig-cb44f27104937682ffaa42ec133e56595e4f08d0.tar.gz
zig-cb44f27104937682ffaa42ec133e56595e4f08d0.zip
std/crypto/hmac: remove HmacBlake2s256 definition
HMAC is a generic construction, so we allow it to be instantiated with any hash function. In practice, HMAC is almost exclusively used with MD5, SHA1 and SHA2, so it makes sense to define some shortcuts for them. However, defining `HmacBlake2s256` is a bit weird (and why specifically that one, and not other hash functions we also support?). There would be nothing wrong with that construction, but it's not used in any standard protocol and would be a curious choice. BLAKE2 being a keyed hash function, it doesn't need HMAC to be used as a MAC, so that also doesn't make it a good example of a possible hash function for HMAC. This commit doesn't remove the ability to use a Hmac(Blake2s256) type if, for some reason, applications really need this, but it removes HmacBlake2s256 as a constant.
Diffstat (limited to 'lib/std')
-rw-r--r--lib/std/crypto/hmac.zig4
1 files changed, 0 insertions, 4 deletions
diff --git a/lib/std/crypto/hmac.zig b/lib/std/crypto/hmac.zig
index 700904555d..5f10b77591 100644
--- a/lib/std/crypto/hmac.zig
+++ b/lib/std/crypto/hmac.zig
@@ -18,10 +18,6 @@ pub const sha2 = struct {
pub const HmacSha512 = Hmac(crypto.hash.sha2.Sha512);
};
-pub const blake2 = struct {
- pub const HmacBlake2s256 = Hmac(crypto.hash.blake2.Blake2s256);
-};
-
pub fn Hmac(comptime Hash: type) type {
return struct {
const Self = @This();