Date: Wed, 9 Aug 2023 14:40:04 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Stefan Bethke <stb@lassitu.de>, freebsd-security@freebsd.org Subject: Re: Downfall microcode update Message-ID: <66285345-7ab9-931a-fbb4-fd988f629e74@grosbein.net> In-Reply-To: <E2A96C20-6F5D-42B0-A16D-BF70CBB6B99B@lassitu.de> References: <E2A96C20-6F5D-42B0-A16D-BF70CBB6B99B@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
09.08.2023 14:30, Stefan Bethke wrote: > https://downfall.page/#faq > > Apparently, Intel will be issuing a microcode update for this. What is the recommended way to automatically apply these during boot? I see that I have cpupdate-g20180513_4 installed, which appears to be maintained despite the scarily old date in the version number :-) https://www.freshports.org/sysutils/cpupdate/ > > The servers I'm concerned about are old enough to not receive BIOS updates ever again. Hi! I maintain the port of cpupdate. Mentioned date corresponds to the version of the utility itself, not to microcodes it uses that are not part of the port/package. Ports users can use one-time "make install-microcodes" convenience helper to download whole bunch of microcode updates for various Intel CPUs. Package users can use one-time "service cpupdate download" that does the same. cpupdate_enable="YES" # in /etc/rc.conf should be enough
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?66285345-7ab9-931a-fbb4-fd988f629e74>