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: <20180531220503.2jqs3oiqsnw7ye2t@khazad-dum.debian.net>
Date:   Thu, 31 May 2018 19:05:03 -0300
From:   Henrique de Moraes Holschuh <hmh@....eng.br>
To:     Ivan Ivanov <qmastery16@...il.com>
Cc:     Josh Boyer <jwboyer@...nel.org>,
        Sherry Hurwitz <sherry.hurwitz@....com>,
        Linux Firmware <linux-firmware@...nel.org>,
        "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
        Rudolf Marek <r.marek@...embler.cz>,
        suravee.suthikulpanit@....com
Subject: Re: [PATCH 1/1] Update AMD cpu microcode for family 15h

On Wed, 30 May 2018, Ivan Ivanov wrote:
> This is still not addressing the outdated 15h microcode version issue
> that Rudolf Marek has pointed out. Also, we still hope to see an
> updated microcode for 16h architecture as well - it has not received
> any updates for two years already

True, but now at least it won't regress old boxes anymore, so we can
ship it in the stable branches of the distros with less restrictions.

It would be really good to be able to actually mitigate spectre v2/v4 on
most AMD systems, though.  And current experience shows this is only
going to happen if we can have the required microcode update also going
through the operating system update channels.

-- 
  Henrique Holschuh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ