From: Jeff Garzik <jgarzik@pobox.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v0] Add SHA-3 hash algorithm
Date: Wed, 03 Oct 2012 03:17:34 -0400 [thread overview]
Message-ID: <506BE68E.5000004@pobox.com> (raw)
In-Reply-To: <20121003071119.GA2571@gondor.apana.org.au>
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
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: David Miller <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v0] Add SHA-3 hash algorithm
Date: Wed, 03 Oct 2012 03:17:34 -0400 [thread overview]
Message-ID: <506BE68E.5000004@pobox.com> (raw)
In-Reply-To: <20121003071119.GA2571@gondor.apana.org.au>
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
next prev parent reply other threads:[~2012-10-03 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 5:45 [PATCH v0] Add SHA-3 hash algorithm Jeff Garzik
2012-10-03 5:45 ` Jeff Garzik
2012-10-03 6:06 ` David Miller
2012-10-03 6:06 ` David Miller
2012-10-03 6:53 ` Jeff Garzik
2012-10-03 6:53 ` Jeff Garzik
2012-10-03 7:11 ` Herbert Xu
2012-10-03 7:11 ` Herbert Xu
2012-10-03 7:17 ` Jeff Garzik [this message]
2012-10-03 7:17 ` Jeff Garzik
2013-04-04 0:29 ` Jeff Garzik
2013-04-04 0:29 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=506BE68E.5000004@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.