Date: Thu, 4 Jan 2018 22:56:11 +1100 From: Darren Reed <darrenr@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Intel CPU design flaw - FreeBSD affected? Message-ID: <5A4E165B.6040809@freebsd.org> In-Reply-To: <CAGfo=8kDVFvuXVf0572LvBY6e3F0XrxDrj_YE6A9puc3T1S3eQ@mail.gmail.com> References: <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net> <CANCZdfra8iS6ptP9Ct401sLum2mZi4dg0KTnkayQjUMbyDc4pQ@mail.gmail.com> <CAGfo=8kDVFvuXVf0572LvBY6e3F0XrxDrj_YE6A9puc3T1S3eQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/01/2018 11:51 AM, Mark Heily wrote: > On Jan 2, 2018 19:05, "Warner Losh" <imp@bsdimp.com> wrote: > > The register article says the specifics are under embargo still. That would > make it hard for anybody working with Intel to comment publicly on the flaw > and any mitigations that may be underway. It would be unwise to assume that > all the details are out until the embargo lifts. > > > Details of the flaws are now published at: > > https://meltdownattack.com The web page has both: meltdown and spectre. Most people are only talking about meltdown which doesn't hit AMD. spectre impacts *both* Intel and AMD. SuSE are making available a microcode patch for AMD 17h processors that disables branch prediction: https://lists.opensuse.org/opensuse-security-announce/2018-01/msg00004.html Kind Regards, Darren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5A4E165B.6040809>