Re: Meltdown workaround enabled?

On 2018-03-13, Brian Camp wrote: > Thats actually the latest version. Even though this board is made by > Intel itself, they have yet to release a BIOS update with the patched > microcode that other OEMs are shipping. BTW, they're actually ECS boards. > re0 at pci3 dev 0

Re: Meltdown workaround enabled?

On 2018-03-14, "Robert Paschedag" wrote: > Errdo I get it right, that a possibly vulnerable CPU > (from 2016) is still vulnerable to MELTDOWN but a newer > BIOS *fakes* the CPU flags so the MELTDOWN "detection code" > says, "this CPU is NOT vulnerable" > > Is that

Re: Meltdown workaround enabled?

Theo de Raadt" <dera...@openbsd.org>, misc@openbsd.org > > Betreff: Re: Meltdown workaround enabled? > > > > Intel make kitty scared... What a fuckmess. > > Errdo I get it right, that a possibly vulnerable CPU > (from 2016) is still vulnerable to MELTDOWN b

Re: Meltdown workaround enabled?

> Gesendet: Mittwoch, 14. März 2018 um 06:13 Uhr > Von: "Bob Beck" <b...@obtuse.com> > An: "Brian Camp" <br...@thecamps.org> > Cc: "Theo de Raadt" <dera...@openbsd.org>, misc@openbsd.org > Betreff: Re: Meltdown workaround enabled? &g

Re: Meltdown workaround enabled?

Intel make kitty scared... What a fuckmess. On Tue, Mar 13, 2018 at 22:57 Brian Camp wrote: > On Tue, Mar 13, 2018 at 10:39 PM, Theo de Raadt > wrote: > >> According to some sources, Intel and a handful of others have known > about the > >> issue since

Re: Meltdown workaround enabled?

> On Tue, Mar 13, 2018 at 10:39 PM, Theo de Raadt wrote: > >> According to some sources, Intel and a handful of others have known about > >> the > >> issue since February 2017(!), so perhaps it has already been patched in the > >> 08Jan2018 BIOS. I too have doubts that to

Re: Meltdown workaround enabled?

On Tue, Mar 13, 2018 at 10:39 PM, Theo de Raadt wrote: >> According to some sources, Intel and a handful of others have known about the >> issue since February 2017(!), so perhaps it has already been patched in the >> 08Jan2018 BIOS. I too have doubts that to date any

Re: Meltdown workaround enabled?

> According to some sources, Intel and a handful of others have known about the > issue since February 2017(!), so perhaps it has already been patched in the > 08Jan2018 BIOS. I too have doubts that to date any processor has been > redesigned to avoid the flaws entirely, but then again... Sure.

Re: Meltdown workaround enabled?

> Running that PoC on the machine while in -current and even 6.1 (no > patches) returns that the system is not vulnerable to meltdown. This > processor was made in 2016 and everything I've read indicates that it > should be vulnerable. Such a low-grade processor may not have sufficient

Re: Meltdown workaround enabled?

On 13 Mar 2018 at 16:57, Mike Larkin wrote: > On Tue, Mar 13, 2018 at 06:20:16PM -0500, Brian Camp wrote: > > On Tue, Mar 13, 2018 at 4:41 PM, Mike Larkin wrote: > > > On Tue, Mar 13, 2018 at 02:23:29PM -0700, Mike Larkin wrote: > > >> On Tue, Mar 13, 2018 at 08:27:49AM

Re: Meltdown workaround enabled?

On Tue, Mar 13, 2018 at 7:18 PM, Chris Cappuccio wrote: > Mike Larkin [mlar...@azathoth.net] wrote: >> >> I'm not sure whether or not I believe what your machine is reporting, I was >> under the assumption that new hardware was needed to fix this. Shrug. >> > > There is a public

Re: Meltdown workaround enabled?

Mike Larkin [mlar...@azathoth.net] wrote: > > I'm not sure whether or not I believe what your machine is reporting, I was > under the assumption that new hardware was needed to fix this. Shrug. > There is a public PoC for meltdown and spectre on OpenBSD: https://github.com/genua/meltdown

Re: Meltdown workaround enabled?

On Tue, Mar 13, 2018 at 06:20:16PM -0500, Brian Camp wrote: > On Tue, Mar 13, 2018 at 4:41 PM, Mike Larkin wrote: > > On Tue, Mar 13, 2018 at 02:23:29PM -0700, Mike Larkin wrote: > >> On Tue, Mar 13, 2018 at 08:27:49AM -0500, Brian Camp wrote: > >> > On Tue, Mar 13, 2018 at

Re: Meltdown workaround enabled?

On Tue, Mar 13, 2018 at 4:41 PM, Mike Larkin wrote: > On Tue, Mar 13, 2018 at 02:23:29PM -0700, Mike Larkin wrote: >> On Tue, Mar 13, 2018 at 08:27:49AM -0500, Brian Camp wrote: >> > On Tue, Mar 13, 2018 at 2:29 AM, Mike Larkin wrote: >> > > On Sun,

Re: Meltdown workaround enabled?

On Tue, Mar 13, 2018 at 02:23:29PM -0700, Mike Larkin wrote: > On Tue, Mar 13, 2018 at 08:27:49AM -0500, Brian Camp wrote: > > On Tue, Mar 13, 2018 at 2:29 AM, Mike Larkin wrote: > > > On Sun, Mar 11, 2018 at 04:33:49PM -0500, Brian Camp wrote: > > >> I have two systems

Re: Meltdown workaround enabled?

On Tue, Mar 13, 2018 at 08:27:49AM -0500, Brian Camp wrote: > On Tue, Mar 13, 2018 at 2:29 AM, Mike Larkin wrote: > > On Sun, Mar 11, 2018 at 04:33:49PM -0500, Brian Camp wrote: > >> I have two systems running 6.2-stable with the meltdown syspatch > >> installed. I noticed

Re: Meltdown workaround enabled?

On 2018-03-13, Brian Camp wrote: > Non-working (Celeron J3455) - > > bcamp@nuc6cayh:~ (OpenBSD 6.2) > $ cpuid 0x0 > eax = 0x001521"" > ebx = 0x756e65471970169159"Genu" > ecx = 0x6c65746e1818588270"ntel" > edx = 0x49656e691231384169

Re: Meltdown workaround enabled?

On Tue, Mar 13, 2018 at 2:29 AM, Mike Larkin wrote: > On Sun, Mar 11, 2018 at 04:33:49PM -0500, Brian Camp wrote: >> I have two systems running 6.2-stable with the meltdown syspatch >> installed. I noticed that while one of them lists "MELTDOWN" in the >> CPU flags, the

Re: Meltdown workaround enabled?

On Sun, Mar 11, 2018 at 04:33:49PM -0500, Brian Camp wrote: > I have two systems running 6.2-stable with the meltdown syspatch > installed. I noticed that while one of them lists "MELTDOWN" in the > CPU flags, the other does not. The one that does not has a Celeron > J3455, which Intel lists as

Meltdown workaround enabled?

I have two systems running 6.2-stable with the meltdown syspatch installed. I noticed that while one of them lists "MELTDOWN" in the CPU flags, the other does not. The one that does not has a Celeron J3455, which Intel lists as affected by meltdown. Does the absence of the MELTDOWN flag mean that