linux-kernel - Re: Linux 2.6.27-rc8

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.WNT.4.63.0809292040140.2188@jbrandeb-desk.amr.corp.intel.com>
Date:	Mon, 29 Sep 2008 20:42:43 -0700 (Pacific Daylight Time)
From:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Arjan van de Ven <arjan@...radead.org>,
	Dave Airlie <airlied@...il.com>, Jiri Kosina <jkosina@...e.cz>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	jesse.brandeburg@...el.com
Subject: Re: Linux 2.6.27-rc8

On Mon, 29 Sep 2008, Linus Torvalds wrote:
> Btw, the _real_ bug is clearly in the hardware design that allows you to 
> brick those things without apparently even having a lock bit.

The hardware has a lock bit, and we're trying to figure out why the BIOS 
writers guide doesn't say to set it.  Probably because of the MAC address, 
but who knows.
 
> I'm hoping Intel doesn't treat this as just a software bug. Some hw 
> designer should be thinking hard about which orifice they put their head 
> up in.

We will post a patch to e1000e tomorrow that sets a lock bit that prevents 
the registers memory mapped by 0:19.0 BAR1 from causing flash write 
cycles.

The patches I've just posted don't quite do that yet.
--
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/