linux-kernel - Re: [PATCH] fix Intel RNG detection

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] [day] [month] [year] [list]

Message-ID: <f96157c40607270851i1e791774i81a557e6f0386c87@mail.gmail.com>
Date:	Thu, 27 Jul 2006 15:51:50 +0000
From:	"gmu 2k6" <gmu2006@...il.com>
To:	"Jan Beulich" <jbeulich@...ell.com>
Cc:	jgarzik@...ox.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fix Intel RNG detection

On 7/27/06, Jan Beulich <jbeulich@...ell.com> wrote:
> ># dmesg | grep rng
> >intel_rng: FWH not detected
> >
> >looks like this ProLiant box with the ICH5 chip has no usable RNG
> >included, or should it?
>
> A configuration like this is what actually motivated me to write the
> patch. You need to remember that the RNG doesn't live in the ICH, but in
> the FWH (which is a different chip not showing up as a separate device
> anywhere) with only some access parameters being configured via the LPC
> device inside the ICH.

well, then let's push it into Linus' tree after the proposed cleanups.
-
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/