Toke Høiland-Jørgensen <[email protected]> writes: > @@ -169,6 +170,12 @@ const struct mac_desc mac_table[ALG_MAX] = { > [ALG_SHA256] = HASH_DESC("Keyed SHA-256", sha256, SHA256), > [ALG_SHA384] = HASH_DESC("Keyed SHA-384", sha384, SHA384), > [ALG_SHA512] = HASH_DESC("Keyed SHA-512", sha512, SHA512), > + [ALG_BLAKE2S] = {"Blake2s", BLAKE2S_SIZE, sizeof(struct > blake2s_context), > + blake2s_bird_init, blake2s_bird_update, > + blake2s_bird_final, BLAKE2S_SIZE, > BLAKE2S_BLOCK_SIZE}, > + [ALG_BLAKE2B] = {"Blake2b", BLAKE2B_SIZE, sizeof(struct > blake2b_context), > + blake2b_bird_init, blake2b_bird_update, > + blake2b_bird_final, BLAKE2B_SIZE, > BLAKE2B_BLOCK_SIZE},
Note that there's an ongoing discussion on the babel@ietf list about whether the output size of Blake2s ought to be truncated to 128 bits. See: https://mailarchive.ietf.org/arch/msg/babel/9EIUxXvaGj-Zm9uktF0v1Zavb-g/ If anyone here has an opinion on this, please weigh in on that list; otherwise I plan to respin this series with an option to have both 128-bit and 256-bit outputs from Blake2s. -Toke
