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:   Mon, 12 Feb 2018 13:56:15 +0000
From:   "Van De Ven, Arjan" <arjan.van.de.ven@...el.com>
To:     David Woodhouse <dwmw2@...radead.org>,
        Alexander Sergeyev <sergeev917@...il.com>
CC:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        "x86@...nel.org" <x86@...nel.org>, Kyle Huey <me@...ehuey.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Levin, Alexander (Sasha Levin)" <alexander.levin@...izon.com>,
        Peter Zijlstra <peterz@...radead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: update spectre v2 microcodes blacklist

> > Raw diff between the mainline blacklist and the bulletin looks like:
> > @@ -1,5 +1,6 @@
> >  { INTEL_FAM6_BROADWELL_CORE,     0x04, 0x28 },
> >  { INTEL_FAM6_BROADWELL_GT3E,     0x01, 0x1b },
> > +{ INTEL_FAM6_BROADWELL_X,        0x01, 0x0b000023 },
> >  { INTEL_FAM6_BROADWELL_X,        0x01, 0x0b000025 },
> 
> That's redundant since blacklisting 0x0b000025 will also stop us from
> using 0x0b000023 anyway.

and 23 is the pre security version so known good.



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ