From nobody Wed Jul 13 09:58:36 2022
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 0C5761CFEF42
	for <freebsd-security@mlmmj.nyi.freebsd.org>; Wed, 13 Jul 2022 09:58:45 +0000 (UTC)
	(envelope-from rfg@tristatelogic.com)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118])
	by mx1.freebsd.org (Postfix) with ESMTP id 4LjY3l6rJ1z3bH5
	for <freebsd-security@freebsd.org>; Wed, 13 Jul 2022 09:58:43 +0000 (UTC)
	(envelope-from rfg@tristatelogic.com)
Received: by segfault.tristatelogic.com (Postfix, from userid 1237)
	id EC8E94E7D0; Wed, 13 Jul 2022 02:58:36 -0700 (PDT)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: freebsd-security@freebsd.org
Subject: Re: Retbleed, another speculative execution attack
In-Reply-To: <CAD2Ti29HLDqiK0JC6A+UY_FHECooNRFsd_V7HxuskUSt0kdSUQ@mail.gmail.com>
List-Id: Security issues <freebsd-security.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-security
List-Help: <mailto:freebsd-security+help@freebsd.org>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Subscribe: <mailto:freebsd-security+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-security+unsubscribe@freebsd.org>
Sender: owner-freebsd-security@freebsd.org
X-BeenThere: freebsd-security@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <95025.1657706316.1@segfault.tristatelogic.com>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 13 Jul 2022 02:58:36 -0700
Message-ID: <95026.1657706316@segfault.tristatelogic.com>
X-Rspamd-Queue-Id: 4LjY3l6rJ1z3bH5
X-Spamd-Bar: ---
Authentication-Results: mx1.freebsd.org;
	dkim=none;
	dmarc=none;
	spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com
X-Spamd-Result: default: False [-3.19 / 15.00];
	NEURAL_HAM_SHORT(-1.00)[-1.000];
	NEURAL_HAM_MEDIUM(-1.00)[-1.000];
	NEURAL_HAM_LONG(-0.99)[-0.992];
	R_SPF_ALLOW(-0.20)[+mx];
	RCVD_NO_TLS_LAST(0.10)[];
	MIME_GOOD(-0.10)[text/plain];
	FROM_EQ_ENVFROM(0.00)[];
	R_DKIM_NA(0.00)[];
	MLMMJ_DEST(0.00)[freebsd-security];
	MIME_TRACE(0.00)[0:+];
	MID_RHS_MATCH_FROMTLD(0.00)[];
	ARC_NA(0.00)[];
	RCPT_COUNT_ONE(0.00)[1];
	FROM_HAS_DN(0.00)[];
	ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US];
	TO_MATCH_ENVRCPT_ALL(0.00)[];
	DMARC_NA(0.00)[tristatelogic.com];
	TO_DN_NONE(0.00)[];
	RCVD_COUNT_TWO(0.00)[2]
X-ThisMailContainsUnwantedMimeParts: N

In message <CAD2Ti29HLDqiK0JC6A+UY_FHECooNRFsd_V7HxuskUSt0kdSUQ@mail.gmail=
.com>, =

grarpamp <grarpamp@gmail.com> wrote:

>On 7/12/22, mike tancsa <mike@sentex.net> wrote:
>>> Just wondering how this might impact FreeBSD ?
>>
>> https://news.ycombinator.com/item?id=3D32071949
>>
>> https://comsec.ethz.ch/research/microarch/retbleed/
>
>FreeBSD should keep a wiki table of all these
>HW attacks with at least three columns...
>- The exploit
>- Were mitigations published
>- Were those or others applied
>
>Point everyone there.

I second that emotion!


Regards,
rfg