From owner-freebsd-security@freebsd.org Thu Jan 4 01:54:00 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 AB6D3EBD325 for ; Thu, 4 Jan 2018 01:54:00 +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 874CB72345 for ; Thu, 4 Jan 2018 01:54:00 +0000 (UTC) (envelope-from joey@joeykelly.net) Received: from localhost (localhost [127.0.0.1]) by safegreet.com (Postfix) with ESMTP id 8672D42BC for ; Wed, 3 Jan 2018 19:53:58 -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 90hzc5fK5yty for ; Wed, 3 Jan 2018 19:53:57 -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 9BB2C42B8 for ; Wed, 3 Jan 2018 19:53:57 -0600 (CST) From: Joey Kelly To: "freebsd-security@freebsd.org" Subject: Re: Intel hardware bug Date: Wed, 03 Jan 2018 20:54:15 -0500 Message-ID: <2347560.AJVtGcUuTT@elisha.atlnet> User-Agent: KMail/4.14.10 (Linux/4.9.67; KDE/4.14.38; x86_64; ; ) In-Reply-To: References: <19097.1515012519@segfault.tristatelogic.com> <2888082.RoyTJcGtdE@elisha.atlnet> 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\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2018 01:54:00 -0000 On Thursday, January 04, 2018 02:44:45 AM Oliver Pinter wrote: > On Thursday, January 4, 2018, Joey Kelly wrote: > > 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. > > Nope. See this part of announcement : > > "Intel believes these exploits do not have the potential to corrupt, modify > or delete data.ntel believes these exploits do not have the potential to > corrupt, modify or delete data." > > There are no statement about _reading_ kernel or other memory, only about > compromising. ;) > No, I mean their lame excuses, dances around the truth, claiming many other platforms AND OPERATING SYSTEMS do it too. 'Tain't so. This is hardware, INTEL hardware, and not an OS problem (though it's an OS band-aid, as someone put it, OS vendors have to wipe Intel's, you know, since they can't wipe it themselves). -- Joey Kelly Minister of the Gospel and Linux Consultant http://joeykelly.net 504-239-6550