From owner-freebsd-security@freebsd.org  Wed Jan  3 20:48:47 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 22FD0EAEC33
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Wed,  3 Jan 2018 20:48:47 +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 101A965BFB
 for <freebsd-security@freebsd.org>; Wed,  3 Jan 2018 20:48:46 +0000 (UTC)
 (envelope-from rfg@tristatelogic.com)
Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1])
 by segfault.tristatelogic.com (Postfix) with ESMTP id 380EC3AE87
 for <freebsd-security@freebsd.org>; Wed,  3 Jan 2018 12:48:40 -0800 (PST)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: "freebsd-security@freebsd.org" <freebsd-security@freebsd.org>
Subject: Re: Intel hardware bug
In-Reply-To: <477ab39d-286d-d9a2-d31e-fd5f7f1679a8@sentex.net>
Date: Wed, 03 Jan 2018 12:48:39 -0800
Message-ID: <19097.1515012519@segfault.tristatelogic.com>
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: Wed, 03 Jan 2018 20:48:47 -0000


In message <477ab39d-286d-d9a2-d31e-fd5f7f1679a8@sentex.net>, 
Mike Tancsa <mike@sentex.net> wrote:

>I am guessing this will impact FreeBSD as well ?
>
>http://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/

Swell.  Just swell.

Why couldn't this have been announced the week -before- I bought an Intel
processor and motherboard to replace my aging AMD rig, rather than the week
-after- I did so?

Geeeesssh!