From owner-freebsd-security@freebsd.org  Wed Jan  3 02:04:24 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 50FF1EA47F3
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Wed,  3 Jan 2018 02:04:24 +0000 (UTC)
 (envelope-from joey@joeykelly.net)
Received: from safegreet.com (safegreet.com [173.230.129.132])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2F95A7DF81
 for <freebsd-security@freebsd.org>; Wed,  3 Jan 2018 02:04:23 +0000 (UTC)
 (envelope-from joey@joeykelly.net)
Received: from localhost (localhost [127.0.0.1])
 by safegreet.com (Postfix) with ESMTP id CA11242B8
 for <freebsd-security@freebsd.org>; Tue,  2 Jan 2018 19:56:34 -0600 (CST)
X-Virus-Scanned: amavisd-new at safegreet.com
Received: from safegreet.com ([127.0.0.1])
 by localhost (safegreet.com [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id TNP-pwDy9f8K for <freebsd-security@freebsd.org>;
 Tue,  2 Jan 2018 19:56:34 -0600 (CST)
Received: from elisha.atlnet (c-24-30-30-53.hsd1.ga.comcast.net [24.30.30.53])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by safegreet.com (Postfix) with ESMTPSA id 0D35C4260
 for <freebsd-security@freebsd.org>; Tue,  2 Jan 2018 19:56:34 -0600 (CST)
From: Joey Kelly <joey@joeykelly.net>
To: freebsd-security@freebsd.org
Subject: Re: Intel hardware bug
Date: Tue, 02 Jan 2018 20:56:50 -0500
Message-ID: <7692356.NWgAdSPsLq@elisha.atlnet>
User-Agent: KMail/4.14.10 (Linux/4.9.67; KDE/4.14.38; x86_64; ; )
In-Reply-To: <477ab39d-286d-d9a2-d31e-fd5f7f1679a8@sentex.net>
References: <477ab39d-286d-d9a2-d31e-fd5f7f1679a8@sentex.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
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 02:04:24 -0000

On Tuesday, January 02, 2018 08:52:27 PM Mike Tancsa wrote:
> I am guessing this will impact FreeBSD as well ?
> 
> http://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/

No way around it. It's hardware FAIL, and ignoring it isn't an option since 
it's apparently a huge hole.

--
Joey Kelly
Minister of the Gospel and Linux Consultant
http://joeykelly.net
504-239-6550