linux-kernel - Re: [PATCH v0] Add SHA-3 hash algorithm

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <506BE68E.5000004@pobox.com>
Date:	Wed, 03 Oct 2012 03:17:34 -0400
From:	Jeff Garzik <jgarzik@...ox.com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
CC:	David Miller <davem@...emloft.net>, linux-crypto@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v0] Add SHA-3 hash algorithm

On 10/03/2012 03:11 AM, Herbert Xu wrote:
> On Wed, Oct 03, 2012 at 02:53:27AM -0400, Jeff Garzik wrote:
>>
>> Maybe my patch is the best we can do in the current kernel, if
>> dynamic digest size is not currently possible. Register "sha3_224",
>> "sha3_256", ... as you describe, and wait for actual users to appear
>> with unsupported digest sizes.
>
> Let's see what people use before we do anything more fancy.
>
> If the variants really start proliferating, we can add a template
> called "trunc" and then have things like "trunc(sha3,224)", etc.

If they start proliferating, you really just want a single "sha3(n)", 
one single shash_alg registered at driver init time.

	Jeff




--
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/