Re: On the matter of OpenBSD breaking embargos (KRACK)

2018-06-19 Thread Kevin Chadwick
On Tue, 19 Jun 2018 09:30:05 -0600 > > > > > ps. Disable Intel Hyper-Threading where not needed, until we all > > > know more. > > > > Is it safer to use bsd.sp for the time being? > > No, a better solution is coming. And in snapshots already. Thankyou for enabling us to patch ASAP.

Re: On the matter of OpenBSD breaking embargos (KRACK)

2018-06-19 Thread Theo de Raadt
Kevin Chadwick wrote: > On Fri, 15 Jun 2018 17:28:14 -0600 > > > > ps. Disable Intel Hyper-Threading where not needed, until we all know > > more. > > Is it safer to use bsd.sp for the time being? No, a better solution is coming. And in snapshots already.

Re: On the matter of OpenBSD breaking embargos (KRACK)

2018-06-19 Thread Kevin Chadwick
On Fri, 15 Jun 2018 17:28:14 -0600 > ps. Disable Intel Hyper-Threading where not needed, until we all know > more. Is it safer to use bsd.sp for the time being?

Re: On the matter of OpenBSD breaking embargos (KRACK)

2018-06-15 Thread Theo de Raadt
Thank you Stefan and Mathy for setting the record straight. This archive is relevant as a followup to comments Gordon Tetlows (FreeBSD Security Officer) made in an audience a week ago (I honestly didn't know who/what until a few hours ago). However, this reconstruction is because others have also

On the matter of OpenBSD breaking embargos (KRACK)

2018-06-15 Thread Stefan Sperling
This a copy of internal discussion between me, Theo, and Mathy Vanhoef about KRACK, from the initial message I received from Mathy, up to today. I am making this public with Theos's and Mathy's consent, without redaction. I have annotated quoted blocks with names to make the discussion a bit easie