Hello, ср, 25 дек. 2019 г. в 14:31, Niels Möller <[email protected]>: > > Daiki Ueno <[email protected]> writes: > > > +static void > > +hmac_md5_set_key_wrapper (void *ctx, const uint8_t *key) > > +{ > > + hmac_md5_set_key (ctx, MD5_BLOCK_SIZE, key); > > +} > > [...] > > > +extern const struct nettle_mac nettle_hmac_md5; > > +extern const struct nettle_mac nettle_hmac_ripemd160; > > +extern const struct nettle_mac nettle_hmac_sha1; > > +extern const struct nettle_mac nettle_hmac_sha224; > > +extern const struct nettle_mac nettle_hmac_sha256; > > +extern const struct nettle_mac nettle_hmac_sha384; > > +extern const struct nettle_mac nettle_hmac_sha512; > > If we define a single nettle_mac for each supported (no-nonce) mac > algorithm, what should the key size be for each algorithm? Using the > underlying block size for the hmac algorithms seems to be a bit > overkill. What key sizes are used in practice? Does it make sense to > use key size equal to digest size (at least, that's what used for hmac > in the ssh protocol)?
Same goes for TLS. Key size = digest size for HMAC. -- With best wishes Dmitry _______________________________________________ nettle-bugs mailing list [email protected] http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
