From owner-freebsd-security@freebsd.org Wed Jan 3 21:08:08 2018 Return-Path: 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 40558EAF658 for ; Wed, 3 Jan 2018 21:08:08 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) by mx1.freebsd.org (Postfix) with ESMTP id 26C69669DE for ; Wed, 3 Jan 2018 21:08:07 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from sweettea.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 9EEAB5651C; Wed, 3 Jan 2018 14:59:36 -0600 (CST) Subject: Re: Intel hardware bug To: "Ronald F. Guilmette" , "freebsd-security@freebsd.org" References: <19097.1515012519@segfault.tristatelogic.com> From: Eric van Gyzen Message-ID: <02563ce4-437c-ab96-54bb-a8b591900ba0@FreeBSD.org> Date: Wed, 3 Jan 2018 14:59:35 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <19097.1515012519@segfault.tristatelogic.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2018 21:08:08 -0000 On 01/03/2018 14:48, Ronald F. Guilmette wrote: > > In message <477ab39d-286d-d9a2-d31e-fd5f7f1679a8@sentex.net>, > Mike Tancsa 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! 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/ Eric