public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [RFC] AES instead of SHA1 for /dev/urandom
@ 2012-12-12  2:03 Ondřej Bílka
  2012-12-12  2:08 ` NeilBrown
  0 siblings, 1 reply; 5+ messages in thread
From: Ondřej Bílka @ 2012-12-12  2:03 UTC (permalink / raw)
  To: linux-kernel

I consider to speed-up /dev/urandom on recent intel processors by
using hardware aes. Same for accelerated aes crypto.

Would you accept a patch if I wrote it?


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [RFC] AES instead of SHA1 for /dev/urandom
  2012-12-12  2:03 [RFC] AES instead of SHA1 for /dev/urandom Ondřej Bílka
@ 2012-12-12  2:08 ` NeilBrown
  2012-12-12  8:58   ` Ondřej Bílka
  0 siblings, 1 reply; 5+ messages in thread
From: NeilBrown @ 2012-12-12  2:08 UTC (permalink / raw)
  To: Ondřej Bílka; +Cc: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

On Wed, 12 Dec 2012 03:03:54 +0100 Ondřej Bílka <neleai@seznam.cz> wrote:

> I consider to speed-up /dev/urandom on recent intel processors by
> using hardware aes. Same for accelerated aes crypto.
> 
> Would you accept a patch if I wrote it?

Have you read  https://lwn.net/Articles/525459  ?

In particular the paragraph containing:

   A member of the audience asked why the kernel couldn't just do away with
   the existing system and use the HWRNG directly.

Does that answer your question in any way?

NeilBrown


> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [RFC] AES instead of SHA1 for /dev/urandom
  2012-12-12  2:08 ` NeilBrown
@ 2012-12-12  8:58   ` Ondřej Bílka
  2012-12-12  9:10     ` NeilBrown
  0 siblings, 1 reply; 5+ messages in thread
From: Ondřej Bílka @ 2012-12-12  8:58 UTC (permalink / raw)
  To: NeilBrown; +Cc: linux-kernel

On Wed, Dec 12, 2012 at 01:08:26PM +1100, NeilBrown wrote:
> On Wed, 12 Dec 2012 03:03:54 +0100 Ondřej Bílka <neleai@seznam.cz> wrote:
> 
> > I consider to speed-up /dev/urandom on recent intel processors by
> > using hardware aes. Same for accelerated aes crypto.
> > 
> > Would you accept a patch if I wrote it?
> 
> Have you read  https://lwn.net/Articles/525459  ?
> 
Yes
> In particular the paragraph containing:
> 
>    A member of the audience asked why the kernel couldn't just do away with
>    the existing system and use the HWRNG directly.
> 
> Does that answer your question in any way?
> 
No as AES is a HWRNG about as much as horse is type of automobile.

Ondra

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [RFC] AES instead of SHA1 for /dev/urandom
  2012-12-12  8:58   ` Ondřej Bílka
@ 2012-12-12  9:10     ` NeilBrown
  2013-01-01 22:50       ` Pavel Machek
  0 siblings, 1 reply; 5+ messages in thread
From: NeilBrown @ 2012-12-12  9:10 UTC (permalink / raw)
  To: Ondřej Bílka; +Cc: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

On Wed, 12 Dec 2012 09:58:16 +0100 Ondřej Bílka <neleai@seznam.cz> wrote:

> On Wed, Dec 12, 2012 at 01:08:26PM +1100, NeilBrown wrote:
> > On Wed, 12 Dec 2012 03:03:54 +0100 Ondřej Bílka <neleai@seznam.cz> wrote:
> > 
> > > I consider to speed-up /dev/urandom on recent intel processors by
> > > using hardware aes. Same for accelerated aes crypto.
> > > 
> > > Would you accept a patch if I wrote it?
> > 
> > Have you read  https://lwn.net/Articles/525459  ?
> > 
> Yes
> > In particular the paragraph containing:
> > 
> >    A member of the audience asked why the kernel couldn't just do away with
> >    the existing system and use the HWRNG directly.
> > 
> > Does that answer your question in any way?
> > 
> No as AES is a HWRNG about as much as horse is type of automobile.

Yes, of course.  Thanks.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [RFC] AES instead of SHA1 for /dev/urandom
  2012-12-12  9:10     ` NeilBrown
@ 2013-01-01 22:50       ` Pavel Machek
  0 siblings, 0 replies; 5+ messages in thread
From: Pavel Machek @ 2013-01-01 22:50 UTC (permalink / raw)
  To: NeilBrown; +Cc: Ondřej Bílka, linux-kernel

On Wed 2012-12-12 20:10:16, NeilBrown wrote:
> On Wed, 12 Dec 2012 09:58:16 +0100 Ondřej Bílka <neleai@seznam.cz> wrote:
> 
> > On Wed, Dec 12, 2012 at 01:08:26PM +1100, NeilBrown wrote:
> > > On Wed, 12 Dec 2012 03:03:54 +0100 Ondřej Bílka <neleai@seznam.cz> wrote:
> > > 
> > > > I consider to speed-up /dev/urandom on recent intel processors by
> > > > using hardware aes. Same for accelerated aes crypto.
> > > > 
> > > > Would you accept a patch if I wrote it?
> > > 
> > > Have you read  https://lwn.net/Articles/525459  ?
> > > 
> > Yes
> > > In particular the paragraph containing:
> > > 
> > >    A member of the audience asked why the kernel couldn't just do away with
> > >    the existing system and use the HWRNG directly.
> > > 
> > > Does that answer your question in any way?
> > > 
> > No as AES is a HWRNG about as much as horse is type of automobile.
> 
> Yes, of course.  Thanks.

Dunno. Some people don't trust HWRNG for various reasons.... (what if
it malfunctions? what if it is backdoored?)

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-01-01 22:50 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-12  2:03 [RFC] AES instead of SHA1 for /dev/urandom Ondřej Bílka
2012-12-12  2:08 ` NeilBrown
2012-12-12  8:58   ` Ondřej Bílka
2012-12-12  9:10     ` NeilBrown
2013-01-01 22:50       ` Pavel Machek

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox