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: Thu, 07 Dec 2006 16:19:56 +0100 [thread overview]
Message-ID: <1165504796.5607.17.camel@bender> (raw)
In-Reply-To: <200612071606.33951.arnd@arndb.de>
On Thu, 2006-12-07 at 16:06 +0100, Arnd Bergmann wrote:
> On Friday 01 December 2006 14:19, Jan Glauber wrote:
> > I've chosen the char driver since it allows the user to decide which pseudo-random
> > numbers he wants to use. That means there is a new interface for the s390
> > PRNG, called /dev/prandom.
> >
> > I would like to know if there are any objections, especially with the chosen device
> > name.
>
> This may be a stupid question, but what is it _good_ for? My understanding is
> that the crypt_s390_kmc() opcodes work in user mode as well as kernel mode, so
> you should not need a character device at all, but maybe just a small tool
> that spits prandom data to stdout.
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.
Jan
next prev parent reply other threads:[~2006-12-07 15:56 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 [this message]
2006-12-07 18:43 ` Arnd Bergmann
2006-12-08 11:42 ` Jan Glauber
[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=1165504796.5607.17.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox