From: Pavel Machek <pavel@ucw.cz>
To: NeilBrown <neilb@suse.de>
Cc: "Ondřej Bílka" <neleai@seznam.cz>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] AES instead of SHA1 for /dev/urandom
Date: Tue, 1 Jan 2013 23:50:29 +0100 [thread overview]
Message-ID: <20130101225029.GA9001@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20121212201016.5342ce32@notabene.brown>
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
prev parent reply other threads:[~2013-01-01 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 2:03 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 message]
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=20130101225029.GA9001@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=neleai@seznam.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®