Date: Thu, 4 Jan 2018 02:44:45 +0100 From: Oliver Pinter <oliver.pinter@hardenedbsd.org> To: Joey Kelly <joey@joeykelly.net> Cc: "freebsd-security@freebsd.org" <freebsd-security@freebsd.org> Subject: Re: Intel hardware bug Message-ID: <CAPQ4fftbw=w3uaU%2BXaVXqis-T3nwLsW=Q=dYXK9UUjBo640Pjg@mail.gmail.com> In-Reply-To: <2888082.RoyTJcGtdE@elisha.atlnet> References: <19097.1515012519@segfault.tristatelogic.com> <02563ce4-437c-ab96-54bb-a8b591900ba0@FreeBSD.org> <2888082.RoyTJcGtdE@elisha.atlnet>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, January 4, 2018, Joey Kelly <joey@joeykelly.net> 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. ;) > > -- > Joey Kelly > Minister of the Gospel and Linux Consultant > http://joeykelly.net > 504-239-6550 > _______________________________________________ > freebsd-security@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org > " >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPQ4fftbw=w3uaU%2BXaVXqis-T3nwLsW=Q=dYXK9UUjBo640Pjg>