From eugen@grosbein.net Wed Aug 9 07:40:04 2023 X-Original-To: freebsd-security@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RLMRX0xP9z4mLtT for ; Wed, 9 Aug 2023 07:40:40 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RLMRW5YYHz4V6K for ; Wed, 9 Aug 2023 07:40:39 +0000 (UTC) (envelope-from eugen@grosbein.net) Authentication-Results: mx1.freebsd.org; none Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.17.1/8.17.1) with ESMTPS id 3797eToX026724 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Wed, 9 Aug 2023 07:40:30 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: stb@lassitu.de Received: from [10.58.0.11] (dadvw [10.58.0.11] (may be forged)) by eg.sd.rdtc.ru (8.17.1/8.17.1) with ESMTPS id 3797eReD070634 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 9 Aug 2023 14:40:28 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Downfall microcode update To: Stefan Bethke , freebsd-security@freebsd.org References: From: Eugene Grosbein Message-ID: <66285345-7ab9-931a-fbb4-fd988f629e74@grosbein.net> Date: Wed, 9 Aug 2023 14:40:04 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 List-Id: Security issues List-Archive: https://lists.freebsd.org/archives/freebsd-security List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-security@freebsd.org X-BeenThere: freebsd-security@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT autolearn=disabled version=3.4.6 X-Spam-Report: * -0.0 SHORTCIRCUIT No description available. * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on hz.grosbein.net X-Rspamd-Queue-Id: 4RLMRW5YYHz4V6K X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE] 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