On 10/03/2012 01:45 AM, Jeff Garzik wrote:
Whee -- SHA-3 is out! I wanted to explore the new toy a bit, and
so, here is a blatantly untested rough draft of SHA-3 kernel support.
Why rough draft? Because answers to the questions below will inform a
more polished version.
Just to update
On 10/03/2012 01:45 AM, Jeff Garzik wrote:
Whee -- SHA-3 is out! I wanted to explore the new toy a bit, and
so, here is a blatantly untested rough draft of SHA-3 kernel support.
Why rough draft? Because answers to the questions below will inform a
more polished version.
Just to update
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
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
On 10/03/2012 02:06 AM, David Miller wrote:
From: Jeff Garzik
Date: Wed, 3 Oct 2012 01:45:42 -0400
1) tcrypt setup blatantly wrong. What is the best setup here? Define a
separate entry for each digest length? Is there some special string
descriptor format that is desired, like "sha3-256"
From: Jeff Garzik
Date: Wed, 3 Oct 2012 01:45:42 -0400
> 1) tcrypt setup blatantly wrong. What is the best setup here? Define a
> separate entry for each digest length? Is there some special string
> descriptor format that is desired, like "sha3-256" or "sha3(256)"?
Good question. The base
From: Jeff Garzik j...@garzik.org
Date: Wed, 3 Oct 2012 01:45:42 -0400
1) tcrypt setup blatantly wrong. What is the best setup here? Define a
separate entry for each digest length? Is there some special string
descriptor format that is desired, like sha3-256 or sha3(256)?
Good question.
On 10/03/2012 02:06 AM, David Miller wrote:
From: Jeff Garzik j...@garzik.org
Date: Wed, 3 Oct 2012 01:45:42 -0400
1) tcrypt setup blatantly wrong. What is the best setup here? Define a
separate entry for each digest length? Is there some special string
descriptor format that is desired,
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.
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
10 matches
Mail list logo
