zig

commit e7b60b219be3885718425d8ddf25d38d3808e90e (tree)
parent 2e354c387e5b5f9a033c29e622ea4a4dbb04bccb
Author: Frank Denis <github@pureftpd.org>
Date:   Mon,  2 Nov 2020 23:56:26 +0100

std/crypto: don't constrain Gimli hash output to a fixed length

As documented in the comment right above the finalization function,
Gimli can be used as a XOF, i.e. the output doesn't have a fixed
length.

So, allow it to be used that way, just like BLAKE3.

Diffstat:
M
lib/std/crypto/gimli.zig
 | 
4
++--

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/std/crypto/gimli.zig b/lib/std/crypto/gimli.zig
@@ -250,7 +250,7 @@ pub const Hash = struct {
     /// By default, Gimli-Hash provides a fixed-length output of 32 bytes
     /// (the concatenation of two 16-byte blocks).  However, Gimli-Hash can
     /// be used as an “extendable one-way function” (XOF).
-    pub fn final(self: *Self, out: *[digest_length]u8) void {
+    pub fn final(self: *Self, out: []u8) void {
         const buf = self.state.toSlice();
 
         // XOR 1 into the next byte of the state
@@ -262,7 +262,7 @@ pub const Hash = struct {
     }
 };
 
-pub fn hash(out: *[Hash.digest_length]u8, in: []const u8, options: Hash.Options) void {
+pub fn hash(out: []u8, in: []const u8, options: Hash.Options) void {
     var st = Hash.init(options);
     st.update(in);
     st.final(out);