From: Jan Glauber <jan.glauber@de.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-crypto <linux-crypto@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Pseudo-random number generator
Date: Fri, 08 Dec 2006 12:42:15 +0100 [thread overview]
Message-ID: <1165578135.5343.15.camel@bender> (raw)
In-Reply-To: <200612071943.14153.arnd@arndb.de>
On Thu, 2006-12-07 at 19:43 +0100, Arnd Bergmann wrote:
> On Thursday 07 December 2006 16:19, Jan Glauber wrote:
> > Hm, why is /dev/urandom implemented in the kernel?
> >
> > It could be done completely in user-space (like libica already does)
> > but I think having a device node where you can read from is the simplest
> > implementation. Also, if we can solve the security flaw we could use it
> > as replacement for /dev/urandom.
>
> urandom is more useful, because can't be implemented in user space at
> all. /dev/urandom will use the real randomness from the kernel as a seed
> without depleting the entropy pool. How does your /dev/prandom device
> compare to /dev/urandom performance-wise? If it can be made to use
> the same input data and it turns out to be significantly faster, I can
> see some use for it.
The performance of the PRNG without constantly adding entropy is up tp
factor 40 faster than /dev/urandom ;- , depending on the block size of
the read.
With the current patch it performs not so well because of the STCKE loop
before every KMC. I think about removing them and changing the
periodically seed to use get_random_bytes instead.
Jan
next prev parent reply other threads:[~2006-12-08 11:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 13:19 [RFC][PATCH] Pseudo-random number generator Jan Glauber
2006-12-01 13:39 ` Alan
2006-12-01 15:20 ` Jan Glauber
2006-12-01 15:37 ` Alan
2006-12-04 16:15 ` Valdis.Kletnieks
2006-12-05 13:07 ` Jan Glauber
2007-01-16 14:07 ` Jan Glauber
2006-12-07 15:06 ` Arnd Bergmann
2006-12-07 15:19 ` Jan Glauber
2006-12-07 18:43 ` Arnd Bergmann
2006-12-08 11:42 ` Jan Glauber [this message]
[not found] <7ngD0-8fX-11@gated-at.bofh.it>
[not found] ` <7ngMA-8D-39@gated-at.bofh.it>
[not found] ` <7niv3-4sQ-21@gated-at.bofh.it>
[not found] ` <7niEE-4Mk-5@gated-at.bofh.it>
2006-12-01 17:33 ` Bodo Eggert
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=1165578135.5343.15.camel@bender \
--to=jan.glauber@de.ibm.com \
--cc=arnd@arndb.de \
--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.