Herbert Xu wrote:
On Wed, Mar 07, 2012 at 03:12:37PM -0500, Jarod Wilson wrote:
Commit bc74b0c8af17458ecae77f725e507ab5fd100105 added proper hmac sha384
and sha512 variants with truncation lengths of 192 and 256 respectively,
per RFC4868:
No, it was done deliberately to maintain backwards compatibility.
Userspace should set the truncbits explicitly from now on.
Okay, I suspected that might be the case. No plans to ever invert that,
so that userspace has to explicitly set the shorter truncbits for
backwards compat?
--
Jarod Wilson
jarod@xxxxxxxxxx.
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
