Read on Twitter
From what I understand, the latest #OpenBSD vs #Intel thing went a little bit like that:
- OpenBSD: Can we be a part of this rumored Intel bug embargo?
- Intel: No. Go away.
- OpenBSD: Can we be a part of this rumored Intel bug embargo?
- Intel: No. Go away.
- OpenBSD: dev do their homework, fix FPU bug, publish patch.
- Theo (at @BSDCan): we are worried, we don't have access to info. Please help us.
- Intel: publishes official advisory: intel.com/content/www/us…
- Theo (at @BSDCan): we are worried, we don't have access to info. Please help us.
- Intel: publishes official advisory: intel.com/content/www/us…
Now everybody and their dogs are going crazy over #OpenBSD developpers doing their jobs , correcting stuff and "violating"an embargo... That they were *never* a part of. Because Intel did not want them to receive information!
As far as I am concerned, Intel has only itself to blame for selling crappy CPUs for years and refusing to communicate with a team because the big $$$ is with Linux, AWS and Google.
The #OpenBSD devs stood up for their OS and for their users. More power to them.
Communication may have been handled better, but let's not forget who is to blame for this whole fiasco: Intel.
Oh, and let's not forget that Theo was greeted with "Shut the f* up" at @BSDCan.
Communication may have been handled better, but let's not forget who is to blame for this whole fiasco: Intel.
Oh, and let's not forget that Theo was greeted with "Shut the f* up" at @BSDCan.
Feel free to disagree with me, but, again, remember this: the kind of issues we are talking about here have been known for about 20 years. #Spectre #Meltdown could have been avoided if Intel had done its homework.
Do not blame the #OpenBSD messenger for something that should have been better managed by other people. End of thread.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
