+ CC net, James Morris
On Wed, Mar 4, 2015 at 7:13 PM, Nicolae Rosia [off-list ref] wrote:
Hello,
I'm trying to understand why icv_truncbits is set to 96 for
hmac(sha256) in xfrm_algo.c because
RFC4868 [1] says that the truncation length for HMAC-SHA256 should be 128.
Am I looking in the wrong place?
[1] https://tools.ietf.org/html/rfc4868#section-2.6
Best regards,
Nicolae Rosia
On Wed, 4 Mar 2015 20:28:26 +0200
Nicolae Rosia [off-list ref] wrote:
On Wed, Mar 4, 2015 at 7:13 PM, Nicolae Rosia [off-list ref] wrote:
quoted
I'm trying to understand why icv_truncbits is set to 96 for
hmac(sha256) in xfrm_algo.c because
RFC4868 [1] says that the truncation length for HMAC-SHA256 should be 128.
See http://comments.gmane.org/gmane.linux.kernel.cryptoapi/6767
Kim
Thank you, Andreas and Kim.
Best regards,
Nicolae Rosia
On Wed, Mar 4, 2015 at 8:38 PM, Kim Phillips [off-list ref] wrote:
On Wed, 4 Mar 2015 20:28:26 +0200
Nicolae Rosia [off-list ref] wrote:
quoted
On Wed, Mar 4, 2015 at 7:13 PM, Nicolae Rosia [off-list ref] wrote:
quoted
I'm trying to understand why icv_truncbits is set to 96 for
hmac(sha256) in xfrm_algo.c because
RFC4868 [1] says that the truncation length for HMAC-SHA256 should be 128.
See http://comments.gmane.org/gmane.linux.kernel.cryptoapi/6767
Kim