mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Schulman.Andrew@epamail.epa.gov
Subject: [PATCH] Re: hw_random and the missing Intel RNGs
Date: Sat, 21 Feb 2004 19:46:23 -0800	[thread overview]
Message-ID: <20040221194623.1b4cc9e7.rddunlap@osdl.org> (raw)


(in reply to:  http://marc.theaimsgroup.com/?l=linux-kernel&m=106816271502140&w=2)

<quoting:>

hw_random has two problems with Intel chipsets:

(1) It fails to detect when no RNG is present.
(2) Intel has stopped putting RNGs into their chipsets.

I've written a description of this problem at
http://home.comcast.net/~andrex/hardware-RNG/index.html.  Here's a summary:
[snipped]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Andrew, I think you should have supplied a patch with your
detailed email.  How's this look?

Does anyone read docs nowadays?

--
~Randy



// Linux linux-263-work
// Document Intel hardware RNG changes.

diffstat:=
 Documentation/hw_random.txt |   12 ++++++++++++
 1 files changed, 12 insertions(+)


diff -Naurp ./Documentation/hw_random.txt~intelrng ./Documentation/hw_random.txt
--- ./Documentation/hw_random.txt~intelrng	2004-02-17 19:58:40.000000000 -0800
+++ ./Documentation/hw_random.txt	2004-02-21 19:38:32.000000000 -0800
@@ -25,6 +25,18 @@ About the Intel RNG hardware, from the f
 	access to our RNG for use as a security feature. At this time,
 	the RNG is only to be used with a system in an OS-present state.
 
+Intel hardware RNG update:
+
+	hw_random has two problems with Intel chipsets:
+
+	(1) It fails to detect when no RNG is present.
+	(2) These products and tools are no longer being manufactured by Intel.
+
+	See <URL:http://home.comcast.net/~andrex/hardware-RNG/index.html>
+	for detailed information.
+	See <URL:http://www.intel.com/design/security/rng/rng.htm>
+	for related product information.
+
 Theory of operation:
 
 	Character driver.  Using the standard open()

                 reply	other threads:[~2004-02-22  3:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040221194623.1b4cc9e7.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=Schulman.Andrew@epamail.epa.gov \
    --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

all inboxes | Powered by JetHome®