From owner-freebsd-security@freebsd.org  Thu Jan  4 01:36:44 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 A1D5BEBB7DD
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Thu,  4 Jan 2018 01:36:44 +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 7C70D71038
 for <freebsd-security@freebsd.org>; Thu,  4 Jan 2018 01:36:44 +0000 (UTC)
 (envelope-from joey@joeykelly.net)
Received: from localhost (localhost [127.0.0.1])
 by safegreet.com (Postfix) with ESMTP id D996F42BC
 for <freebsd-security@freebsd.org>; Wed,  3 Jan 2018 19:36:42 -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 35egBpNl1wN1 for <freebsd-security@freebsd.org>;
 Wed,  3 Jan 2018 19:36:41 -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 C40EE42B8
 for <freebsd-security@freebsd.org>; Wed,  3 Jan 2018 19:36:41 -0600 (CST)
From: Joey Kelly <joey@joeykelly.net>
To: freebsd-security@freebsd.org
Subject: Re: Intel hardware bug
Date: Wed, 03 Jan 2018 20:36:59 -0500
Message-ID: <2888082.RoyTJcGtdE@elisha.atlnet>
User-Agent: KMail/4.14.10 (Linux/4.9.67; KDE/4.14.38; x86_64; ; )
In-Reply-To: <02563ce4-437c-ab96-54bb-a8b591900ba0@FreeBSD.org>
References: <19097.1515012519@segfault.tristatelogic.com>
 <02563ce4-437c-ab96-54bb-a8b591900ba0@FreeBSD.org>
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: Thu, 04 Jan 2018 01:36:44 -0000

On Wednesday, January 03, 2018 02:59:35 PM Eric van Gyzen wrote:

> 
> Wait until Tuesday before you explode.  Intel are now saying that it's
> not a "bug" in Intel CPUs.
> 
> https://newsroom.intel.com/news/intel-responds-to-security-research-findings
> /

Bogus tripe. They're spreading FUD.

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