Issues relating to a bug in Intel cpus(marc.info)
marc.info
Issues relating to a bug in Intel cpus
https://marc.info/?l=openbsd-tech&m=153431475429367&w=2
21 comments
Certain parts of the BSD community keeps leaking stuff early, either by doing commits in public, or by talking about stuff in advance, before all the bits are in place to protect systems. Hell, they already leaked one this year, forcing a huge scramble all round to get patched out of the door. It has been a persistent issue for years. Why on earth would they still expect to be trusted?
It may well be just one or two people doing it, but their actions are screwing things up for an entire set of operating systems.
It's especially critical for coordination to happen on vulnerabilities like this one, where it requires a combination of microcode and kernel patches to be done in sync. If one distribution leaks early, all are put at nearly immediate significant risk.
It may well be just one or two people doing it, but their actions are screwing things up for an entire set of operating systems.
It's especially critical for coordination to happen on vulnerabilities like this one, where it requires a combination of microcode and kernel patches to be done in sync. If one distribution leaks early, all are put at nearly immediate significant risk.
Do other manufacturers have a better relationship with *BSD?
To be honest the attitude of "everything sucks and everything is broken" doesn't help OpenBSD though they are right to complain about some things.
To be honest the attitude of "everything sucks and everything is broken" doesn't help OpenBSD though they are right to complain about some things.
"everything sucks and everything is broken"
Well, looking at all the chips I've bought in servers for the last 5 years, they are not wrong.
Well, looking at all the chips I've bought in servers for the last 5 years, they are not wrong.
I know that nvidia provides native drivers for freebsd, making nvidia gpus the best ones for the platform. I don't know of anything beyond that.
Not really. But sometimes they send a patch or two
https://lists.freebsd.org/pipermail/freebsd-amd64/2011-March...
https://lists.freebsd.org/pipermail/freebsd-amd64/2011-March...
The next message in the thread adds to the insult https://marc.info/?l=openbsd-tech&m=153434075003703&w=2
What's funny is that LWN, a Linux news outlet, might have:
What's funny is that LWN, a Linux news outlet, might have:
OpenBSD's history of leaking embargoed information might be a reason here. If you don't play by the rules, the adults don't let you play anymore.
The key quote from Theo:
> We believe Intel cpus do almost no security checks up-front, but defer checks until instruction retire. As a result we believe similar issues will be coming in the future.
> We believe Intel cpus do almost no security checks up-front, but defer checks until instruction retire. As a result we believe similar issues will be coming in the future.
More links:
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/L1TF
https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/L1TF
https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html
There's also a dedicated site: https://foreshadowattack.eu/
Is x86 dead now?
These are bugs related to caching and thus unrelated to cpu architecture.
The core lesson appears to be that Intel has been playing loose with security. That is not a fundamental x86 problem, not so long as AMD is producing competent cpus.
The core lesson appears to be that Intel has been playing loose with security. That is not a fundamental x86 problem, not so long as AMD is producing competent cpus.
Doubtful, maybe if the power architecture was more accessible for gamers and the average individual.
Most ARM & MIPS CPUs just don't yet have the raw power people have come to expect.
Most ARM & MIPS CPUs just don't yet have the raw power people have come to expect.
Discussed here:
https://news.ycombinator.com/item?id=17759762
https://news.ycombinator.com/item?id=17759762
Where? I can't see discussion about this submission at that link.
Hi, if you're a HN mod, please unmark this. It is not a dupe.
Intel's treatment of *BSD is frankly quite insulting, especially so given that they serve a _huge_ portion of the internet traffic, with Netflix using FreeBSD for content delivery.