News for hackers. Stuff that matters.
Re:Disable SMT/Hyperthreading in all Intel BIOSes by wiz21c on Thursday August 23, 2018 @04:07PM (#17830304)
FTA

>>> We are having to do research by reading other operating systems.

Si Intel cooperates with business partners like apple/windows and not with open source. Does it mean that Apple and Windows can claim to be more secure because they have access to the information needed to fix Intel's issues ?

Re:Disable SMT/Hyperthreading in all Intel BIOSes by pkaye on Thursday August 23, 2018 @04:47PM (#17830578)
A lot of these bugs seems to be found by the Google teams and since they are heavy Linux users, I'm sure in many cases they have a solution for Linux before Apple or Microsoft does.
Re:Disable SMT/Hyperthreading in all Intel BIOSes by 2trill2spill on Thursday August 23, 2018 @04:11PM (#17830326)
> Does it mean that Apple and Windows can claim to be more secure because they have access to the information needed to fix Intel's issues ?

They can claim it, but I would trust a Linux or FreeBSD box over MacOS or Windows anytime even if they get some security info before the open source operating systems.

Re:Disable SMT/Hyperthreading in all Intel BIOSes by wmf on Thursday August 23, 2018 @04:22PM (#17830389)
Intel cooperates with organizations that obey embargoes and don't badmouth their partners in public, like Red Hat, Canonical, and probably the Linux Foundation. Intel does not cooperate with OpenBSD.
Re:Disable SMT/Hyperthreading in all Intel BIOSes by abcdef123xyz123 on Thursday August 23, 2018 @05:09PM (#17830727)
OpenBSD has never disobeyed an embargo. Argued for them to be reduced, criticized them, but not disobeyed them.
Re:Disable SMT/Hyperthreading in all Intel BIOSes by DannyBee on Friday August 24, 2018 @01:10AM (#17832920)
i'm pretty sure this is not true: The most recent example i remember is: https://lobste.rs/s/dwzplh/krack_attacks_breaking_wpa2#c_pbh...
Re:Disable SMT/Hyperthreading in all Intel BIOSes by capt8bit on Friday August 24, 2018 @01:39AM (#17833023)
This is common misinformation. Even in this case, OpenBSD did not break the embargo. After protesting, they received the permission of the researcher to publish:

  Note that I wrote and included a suggested diff for OpenBSD already, and that
  at the time the tentative disclosure deadline was around the end of August. As
  a compromise, I allowed them to silently patch the vulnerability.
(https://www.krackattacks.com/#openbsd)
Re:Disable SMT/Hyperthreading in all Intel BIOSes by swixmix on Thursday August 23, 2018 @05:12PM (#17830742)
I think what you're insinuating is a side effect of the OpenBSD group being open, honest, and congruent to their ethics.
Re:Disable SMT/Hyperthreading in all Intel BIOSes by DannyBee on Friday August 24, 2018 @01:12AM (#17832924)
What he's insinuating is that they agreed to embargos and then repeatedly broke them, claiming it was "better for users".

Regardless of whether it is, you should expect the result of that to be that nobody trusts them with embargoes.

Which is in fact, what has happened.

Re:Disable SMT/Hyperthreading in all Intel BIOSes by swixmix on Friday August 24, 2018 @06:23AM (#17834016)
The KRACK embargo expired as per agreement but I'll partially concede after reading about this OpenSSL accident: https://www.tedunangst.com/flak/post/regarding-embargoes

Google broke an embargo early. https://security.googleblog.com/2018/01/todays-cpu-vulnerabi...

EFail embargo was broken. See https://twitter.com/seecurity/status/995964977461776385 and http://flaked.sockpuppet.org/2018/05/16/a-unified-timeline.h...

I don't think picking on OpenBSD is the right thing here.

Re:Disable SMT/Hyperthreading in all Intel BIOSes by saas_co_de on Friday August 24, 2018 @04:58AM (#17833674)
> badmouth

a.k.a. truth

Linus has "badmouthed" Intel in much harsher and more explicit terms. Linux is just too big for them to get away with trying to smear and slander so they ignore him and move on.

Re:Disable SMT/Hyperthreading in all Intel BIOSes by ars on Thursday August 23, 2018 @05:08PM (#17830719)
I think they mean Linux, not Apple/Windows.