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" or
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.
Code notes and questions:
1) tcrypt setup blatantly wrong. What
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 n
Hi All,
I see that there is no specific core driver or framework for GMAC and CMAC mode.
My hardware accelerator has support for GMAC and CMAC modes, how to I
proceed with writing a driver for the same?
Thanks and Regards,
Arun R Murthy
-
--
To unsubscribe from this list: send
From: Stephen Warren
Nothing from this file is used, and the file will hopefully be deleted
soon.
Signed-off-by: Stephen Warren
---
Herbert, if this patch can get into 3.7 (it's late, I know) then that
would be great. If not, may I please request an ack so I can take the
change through the Tegr
Rusty Russell wrote:
> Right. I think we need to use different names for generated vs supplied
> files
The problem with supplied files is people who do allyesconfig, allmodconfig
and randconfig just to test things finding that their builds break. The
kernel build magic is not really set up to
On Tue, Oct 02, 2012 at 12:58:03PM +0930, Rusty Russell wrote:
> Josh Boyer writes:
>
> > On Sat, Sep 29, 2012 at 08:13:25AM +0100, David Howells wrote:
> >> Rusty Russell wrote:
> >>
> >> > [2.808075] Loading module verification certificates
> >> > [2.809331] X.509: Cert 6e03943da0f3b0
