From owner-freebsd-security@freebsd.org  Thu Jan  4 14:51:16 2018
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B137EB9C33
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Thu,  4 Jan 2018 14:51:16 +0000 (UTC) (envelope-from des@des.no)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id 01A996CBD3
 for <freebsd-security@freebsd.org>; Thu,  4 Jan 2018 14:51:15 +0000 (UTC)
 (envelope-from des@des.no)
Received: from desk.des.no (smtp.des.no [194.63.250.102])
 by smtp.des.no (Postfix) with ESMTP id 87A691045C;
 Thu,  4 Jan 2018 14:51:14 +0000 (UTC)
Received: by desk.des.no (Postfix, from userid 1001)
 id 2668F5CE07; Thu,  4 Jan 2018 14:49:42 +0000 (UTC)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Eric McCorkle <eric@metricspace.net>
Cc: freebsd-security@freebsd.org
Subject: Re: Intel hardware bug
References: <19097.1515012519@segfault.tristatelogic.com>
 <02563ce4-437c-ab96-54bb-a8b591900ba0@FreeBSD.org>
 <7C58A6DB-0760-4E5A-B65D-2ED6A6B7AAD2@acsalaska.net>
 <867esy2vwz.fsf@desk.des.no>
 <0bb7ffc6-fa51-98db-9dc1-1bd49e1c7b44@metricspace.net>
Date: Thu, 04 Jan 2018 15:49:41 +0100
In-Reply-To: <0bb7ffc6-fa51-98db-9dc1-1bd49e1c7b44@metricspace.net> (Eric
 McCorkle's message of "Wed, 3 Jan 2018 22:01:45 -0500")
Message-ID: <86zi5tu1a2.fsf@desk.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2018 14:51:16 -0000

Eric McCorkle <eric@metricspace.net> writes:
> Given enough skill, resources, and motivation, it's likely that an
> attacker could craft a javascript-based version of the attack, then
> every javascript website (aka all of them) is a potential attack vector.

Uh, this has already been demonstrated.  According to Google, Chrome 64
(to be released in a few days) includes countermeasures against it.  I
don't have any further details.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no