Date: Mon, 19 Mar 2018 11:28:46 +0100 From: Andrea Venturoli <ml@netfence.it> To: Jan Demter <jan-mailinglists@demter.de>, freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-18:03.speculative_execution Message-ID: <7599974f-d31e-4df1-0b82-6b401461dcca@netfence.it> In-Reply-To: <8deba9d2-17b5-9088-1766-42f9e334df89@demter.de> References: <20180314042924.E880D1128@freefall.freebsd.org> <337d9fd4-2aa4-609a-6a00-e9ce2be599cc@netfence.it> <8deba9d2-17b5-9088-1766-42f9e334df89@demter.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/18/18 18:54, Jan Demter wrote: >> Of course I find this enabled on the Intel box and not on the AMD one, >> but... is PTI in any way affected by a microcode update from Intel? > > From what I have read so far, I'm pretty certain it isn't planned or > even possible to patch this via a microcode update. Ok, I'm wrong then: I understood Spectre was unfixable, while Intel had provided (or was going to provide) a microcode update to patch (not mitigate) MeltDown. Of course PTI might be a good idea in any case. > For Intel CPUs, there's this list: > https://newsroom.intel.com/wp-content/uploads/sites/11/2018/03/microcode-update-guidance.pdf Thanks. Altough I was looking for AMD mostly :) > The microcode update itself will work, if that is what you meant, but > just updating the microcode and not FreeBSD is useless to mitigate > Spectre V2. Again, my fault: the "Please update your system in order to update CPU microcode." message led me to a wrong conclusion. bye & Thanks av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7599974f-d31e-4df1-0b82-6b401461dcca>