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  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, 20 Nov 2006 18:45:35 -0500
From:	Dave Jones <>
To:	Chris Wright <>
	Justin Forbes <>,
	Zwane Mwaikambo <>,
	"Theodore Ts'o" <>,
	Randy Dunlap <>,
	Chuck Wolber <>,
	Chris Wedgwood <>,
	Michael Krufky <>,,,,
	Jan Beulich <>,
	Metathronius Galabant <>,
	Michael Buesch <>,
	Greg Kroah-Hartman <>
Subject: Re: [PATCH 46/61] fix Intel RNG detection

On Tue, Oct 31, 2006 at 09:34:26PM -0800, Chris Wright wrote:
 > From: Jan Beulich <>
 > [PATCH] fix Intel RNG detection
 > Previously, since determination whether there was an Intel random number
 > generator was based on a single bit, on systems with a matching bridge
 > device but without a firmware hub, there was a 50% chance that the code
 > would incorrectly decide that the system had an RNG.  This patch adds
 > detection of the firmware hub to better qualify the existence of an RNG.
 > There is one issue with the patch: I was unable to determine the LPC
 > equivalent for the PCI bridge 8086:2430 (since the old code didn't care
 > about which of the many devices provided by the ICH/ESB it was chose to use
 > the PCI bridge device, but the FWH settings live in the LPC device, so the
 > device list needed to be changed).
 > Signed-off-by: Jan Beulich <>
 > Signed-off-by: Michael Buesch <>
 > Signed-off-by: Andrew Morton <>
 > Signed-off-by: Linus Torvalds <>
 > Signed-off-by: Greg Kroah-Hartman <>
 > Signed-off-by: Chris Wright <>

Since I pushed an update to our Fedora users based on, a few people
have reported they no longer have their RNG's detected.
Here's one report:


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists