this post was submitted on 26 Jul 2023
70 points (98.6% liked)

Privacy

31833 readers
183 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

The bug allows attackers to swipe data from a CPU's registers. [...] the exploit doesn't require physical hardware access and can be triggered by loading JavaScript on a malicious website.

you are viewing a single comment's thread
view the rest of the comments
[–] SatanicNotMessianic@lemmy.ml 6 points 1 year ago (6 children)

I’m curious - does this kind of report make people less likely to go with an AMD cpu? The last time I was thinking about building a new pc, AMD had just definitively taken the lead in speed per dollar, and I would have gone with one of the higher end chips. I’m not sure whether this would have affected my decision, but I’d probably be concerned with performance degradation as well as the security issue. I’d have waited for the patch to buy a system with updated firmware, but Od still want to see what the impact was as well as learn more about the exploit and whether there were additional issues.

I ended up just getting a steam deck and all of my other computers are macs, so it’s hard to put myself back into the builder’s/buyer’s headspace.

[–] floofloof@lemmy.ca 17 points 1 year ago (1 children)

does this kind of report make people less likely to go with an AMD cpu?

I doubt it, since Intel has its share of similar CPU security issues. For several generations the understanding has been that Intel's CPUs arrive with impressive performance on day 1, then gradually leak that performance away as security issues are patched over subsequent months.

[–] SatanicNotMessianic@lemmy.ml 4 points 1 year ago

Thanks! That’s exactly the kind of insight I was hoping for.

[–] neardeaf@lemm.ee 9 points 1 year ago (3 children)

Honestly no. Remember Spectre & Meltdown vulnerabilities back in 2018? Yeah that security bug that only affected Intel CPUs until it was patched seriously told consumers and enterprise customers to “please turn off hyperthreading” to prevent exposure. Fucking LOL. Voluntarily cut my CPU performance in half!? Based on a theoretical exploit that was only found in a very specific and controlled environment before everyone started FREAKING out?

[–] SatanicNotMessianic@lemmy.ml 3 points 1 year ago

I’ve been out of the builder world for long enough that I didn’t follow the 2018 bug. I’m more from the F00F generation in any case. I also took a VLSI course somewhere in the mid-90s that convinced me to do anything other than design chips. I seem to remember something else from that era where a firmware based security bug related to something I want to say was browser-based, but it wasn’t the CPU iirc.

In any case, I get the point you and others are making about evaluating the risks of a security flaw before taking steps that might hurt performance or worrying about it too much.

load more comments (2 replies)
load more comments (4 replies)