linux-kernel - Re: New format Intel microcode...

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: <1183069855.5889.2.camel@laptopd505.fenrus.org>
Date:	Thu, 28 Jun 2007 15:30:55 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Bill Davidsen <davidsen@....com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Daniel J Blueman <daniel.blueman@...il.com>,
	Shaohua Li <shaohua.li@...el.com>, jamagallon@....com,
	tigran@...azian.fsnet.co.uk,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: New format Intel microcode...


> I was mainly concerned with this being a new issue, and curious if 
> Microsoft was calling an O/S bug a "microcode fix," given that the 
> average Windows user doesn't know microcode from nanotech anyway. The 
> non-answer from Arjan didn't answer either, and started by calling the

then ask questions?
Linux 2.6 is not affected.. what more is there to say? Regardless of
that as I said, Intel recommends always running the most current
microcode. 


> I'd like the microcode update, some people elsewhere speculate that user 
> level code could effect reliability if not security.

those "people" are speculating. Simple as that.

(oh and the microcode update is already there as I said... so what's the
problem?)


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

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