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: <1516967135.2801.1.camel@redhat.com>
Date:   Fri, 26 Jan 2018 12:45:35 +0100
From:   Petr Oros <poros@...hat.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/microcode/intel: print previous microcode revision
 during early update

Borislav Petkov píše v Pá 26. 01. 2018 v 11:41 +0100:
> On Fri, Jan 26, 2018 at 11:34:50AM +0100, Petr Oros wrote:
> >   When kernel do early microcode update, code printing only
> >   new microcode version. But in this case we no have chance
> >   to check which version was in cpu from BIOS vendor.
> 
> And we need that because?
> 


During time of facing the Spectre vulnerability and the requirement of handling
different microcode updates, it has shown, that it would be useful to have
additional information which microcode version was in BIOS, if the early-update
routine will apply an update.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ