| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1165504796.5607.17.camel@bender> Date: Thu, 07 Dec 2006 16:19:56 +0100 From: Jan Glauber <jan.glauber@...ibm.com> To: Arnd Bergmann <arnd@...db.de> Cc: linux-crypto <linux-crypto@...r.kernel.org>, linux-kernel@...r.kernel.org Subject: Re: [RFC][PATCH] Pseudo-random number generator 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists