From owner-freebsd-security@freebsd.org  Thu Jan  4 15:43:01 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 1D362EBDC15
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Thu,  4 Jan 2018 15:43:01 +0000 (UTC)
 (envelope-from eric@metricspace.net)
Received: from mail.metricspace.net (mail.metricspace.net
 [IPv6:2001:470:1f11:617::107])
 by mx1.freebsd.org (Postfix) with ESMTP id E5A036F148
 for <freebsd-security@freebsd.org>; Thu,  4 Jan 2018 15:43:00 +0000 (UTC)
 (envelope-from eric@metricspace.net)
Received: from [192.168.43.57] (mobile-166-171-187-140.mycingular.net
 [166.171.187.140])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate) (Authenticated sender: eric)
 by mail.metricspace.net (Postfix) with ESMTPSA id 5A8508575;
 Thu,  4 Jan 2018 15:18:09 +0000 (UTC)
Subject: Re: Intel hardware bug
To: =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= <des@des.no>
Cc: freebsd-security@freebsd.org
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>
 <86zi5tu1a2.fsf@desk.des.no>
From: Eric McCorkle <eric@metricspace.net>
Message-ID: <867801a5-be19-8f62-fa46-2999d54c0967@metricspace.net>
Date: Thu, 4 Jan 2018 10:18:08 -0500
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <86zi5tu1a2.fsf@desk.des.no>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
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 15:43:01 -0000

On 01/04/2018 09:49, Dag-Erling Smørgrav wrote:
> 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.

This does not surprise me at all.