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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 01 Jun 2009 02:18:07 +0900 (JST)
From:	Atsushi Nemoto <anemo@....ocn.ne.jp>
To:	mpm@...enic.com
Cc:	akpm@...ux-foundation.org, linux-mips@...ux-mips.org,
	ralf@...ux-mips.org, linux-kernel@...r.kernel.org,
	herbert@...dor.apana.org.au
Subject: Re: [PATCH] hwrng: Add TX4939 RNG driver

On Sun, 31 May 2009 12:00:09 -0500, Matt Mackall <mpm@...enic.com> wrote:
> > >From the datasheet:
> > 
> > 	The quality of the random numbers generated immediately after
> > 	reset can be insufficient.  Therefore, do not use random
> > 	numbers obtained from the first and second generations; use
> > 	the ones from the third or subsequent generation.
> 
> Does the datasheet say anything about -how- the random numbers are
> produced? Most physical sources that I'm aware of don't have this sort
> of issue. But some pseudo-RNGs do. So this looks a little worrisome.

Nothing for "how".  If a RNG was actually a pseudo-RNG, does anything
a driver should do?  Any future plan to select one RNG from multiple
sources based on randomness grade?

---
Atsushi Nemoto
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ