Date: Wed, 3 Jan 2018 14:59:35 -0600 From: Eric van Gyzen <vangyzen@FreeBSD.org> To: "Ronald F. Guilmette" <rfg@tristatelogic.com>, "freebsd-security@freebsd.org" <freebsd-security@freebsd.org> Subject: Re: Intel hardware bug Message-ID: <02563ce4-437c-ab96-54bb-a8b591900ba0@FreeBSD.org> In-Reply-To: <19097.1515012519@segfault.tristatelogic.com> References: <19097.1515012519@segfault.tristatelogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/03/2018 14:48, Ronald F. Guilmette wrote: > > In message <477ab39d-286d-d9a2-d31e-fd5f7f1679a8@sentex.net>, > Mike Tancsa <mike@sentex.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?02563ce4-437c-ab96-54bb-a8b591900ba0>