Thank you. After many of the things I have read about OpenBSD being "overhyped" online I thought this was a real interesting case that most of the industry gets slapped with this the other day and OpenBSD is all fine and dandy.
I am glad to get the quantification as to why. Ken On Thu, May 10, 2018 at 03:54:01PM -0700, Mike Larkin wrote: > On Thu, May 10, 2018 at 03:41:59PM +0000, Ken MacKenzie wrote: > > Dare I ask what lead to OpenBSD not being affected. > > > > Sorry if it is a dumb question but since this hit FreeBSD as well I am > > wondering > > what OpenBSD did differently. > > > > Was this caught in an audit? > > > > I am just curious about causality that kept OpenBSD in the clear of this one > > that made such headlines yesterday. > > > > Ken > > > > OpenBSD does not allow userspace to access the hardware debug registers. > > -ml > > > On Thu, May 10, 2018 at 07:39:28AM -0700, Mike Larkin wrote: > > > On Thu, May 10, 2018 at 10:22:48AM -0400, Predrag Punosevac wrote: > > > > Does this > > > > > > > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2018-8897 > > > > > > > > affect 6.3 stable? > > > > > > > > Best, > > > > Predrag > > > > > > > > > > OpenBSD is not affected. > > > > > > -ml > > >
