linux-kernel - Re: [PATCH 2/2] x86, microcode: Make reload interface per system

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]

Date:	Thu, 21 Jun 2012 20:00:59 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Borislav Petkov <bp@...64.org>,
	"Yu, Fenghua" <fenghua.yu@...el.com>, X86-ML <x86@...nel.org>,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Andreas Herrmann <andreas.herrmann3@....com>
Subject: Re: [PATCH 2/2] x86, microcode: Make reload interface per system

On Thu, 21 Jun 2012, Peter Zijlstra wrote:
> On Wed, 2012-06-20 at 20:08 -0300, Henrique de Moraes Holschuh wrote:
> > On Wed, 20 Jun 2012, Peter Zijlstra wrote:
> > > On Wed, 2012-06-20 at 01:28 +0200, Borislav Petkov wrote:
> > > > which makes me wonder whether we still need that OLD INTERFACE.
> > > > Henrique, any thoughts here? 
> > > 
> > > Yes I need it, I've no f'ing clue where to put the ucode image so that
> > > the whole firmware mess can find it :-)
> > 
> > iucode_tool -K <name of intel microcode .dat/.bin file(s)> will do it
> > for you :p
> 
> This thing is not installed on my machine, nor would I have know to look
> for it. Nor does apt-cache search iucode_tool suggest any package.
> 
> IOW fail.

Meh.  I uploaded the first public version of the thing a whole two weeks
ago!  It should have been all over the Internet by now ;-)

It is in Debian Wheezy (soon-to-be-stable) as of yesterday, I think.  It
will eventually end up in Ubuntu.  And if you guys think it is worthwhile to
maintain it upstream either in git.k.o, or as part of tools/, I have nothing
against it.

I posted the URL earlier, I think, but here it is:
http://cdn.debian.net/debian/pool/contrib/i/iucode-tool/iucode-tool_0.8.orig.tar.bz2

But it really exists to help distros do Intel microcode management and
release install-and-forget packages for end users.  End-users should get to
either ignore its existence entirely and get automated updates of microcode
as distro binary packages, or run an "update-intel-microcode" script (not
written yet, but there is one on Debian and Ubuntu's microcode.ctl package)
that downloads the blob from Intel, and does whatever is needed to install
it to /lib/firmware and apply it to the running system (and kernel image,
initramfs, whatever).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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/