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-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
