linux-kernel - Re: [PATCH] xfrm: fix hmac(sha256) truncation length

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F5A0876.3060408@redhat.com>
Date:	Fri, 09 Mar 2012 08:41:10 -0500
From:	Jarod Wilson <jarod@...hat.com>
To:	Herbert Xu <herbert@...dor.hengli.com.au>
CC:	linux-kernel@...r.kernel.org, Paul Wouters <pwouters@...hat.com>,
	"David S. Miller" <davem@...emloft.net>,
	Martin Willi <martin@...ongswan.org>, netdev@...r.kernel.org,
	linux-crypto@...r.kernel.org
Subject: Re: [PATCH] xfrm: fix hmac(sha256) truncation length

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@...hat.com.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/