linux-kernel - Re: [stable] [PATCH 46/61] 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0612140028410.16018@twinlark.arctic.org>
Date:	Thu, 14 Dec 2006 00:40:16 -0800 (PST)
From:	dean gaudet <dean@...tic.org>
To:	Jan Beulich <jbeulich@...ell.com>
cc:	Chris Wright <chrisw@...s-sol.org>,
	Zwane Mwaikambo <zwane@....linux.org.uk>,
	Michael Buesch <mb@...sch.de>,
	Metathronius Galabant <m.galabant@...glemail.com>,
	stable@...nel.org, Michael Krufky <mkrufky@...uxtv.org>,
	Justin Forbes <jmforbes@...uxtx.org>, alan@...rguk.ukuu.org.uk,
	Theodore Ts'o <tytso@....edu>,
	Chris Wedgwood <reviews@...cw.f00f.org>, akpm@...l.org,
	torvalds@...l.org, Chuck Wolber <chuckw@...ntumlinux.com>,
	Dave Jones <davej@...hat.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [stable] [PATCH 46/61] fix Intel RNG detection

On Thu, 14 Dec 2006, Jan Beulich wrote:

> >with the patch it boots perfectly without any command-line args.
> 
> Are you getting the 'Firmware space is locked read-only' message then?

yep...

so let me ask a naive question... don't we want the firmware locked 
read-only because that protects the bios from viruses?  honestly i'm naive 
in this area of pc hardware, but i'm kind of confused why we'd want 
unlocked firmware just so we can detect a RNG.

-dean
-
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/