6 ms·
I'm considering to upgrade my primary computer this summer and considering an AMD system. Following is my thought process: - Maybe I should buy an Intel system
by bayindirh 7y ago
I'm considering to upgrade my primary computer this summer and considering an AMD system. Following is my thought process:
- Maybe I should buy an Intel system again because of the performance counters and other nice things.
Another Intel attack surfaces
- Yep, I shall go AMD this time...
- mynameisvlad 7y agohttps://www.techspot.com/news/84309-amd-cpus-vulnerable-severe-new-side-channel-attack.html https://www.techspot.com/news/84309-amd-cpus-vulnerable-seve... From 2 days ago, in case you weren't aware.
- temac 7y agoThe "new" AMD attack depends on lack of already existing spectre mitigations. If I understand correctly, this one is a real new one that works against a correctly patched system.
- cosmiccatnap 7y agoYou are correct. No AMD vulnerability is in the same universe as the Intel vulnerabilities from this year alone. Good luck on your new build
- afiori 7y agoCuriosity: is this down voted because it is false/exaggerated? As someone that is far from being an expert I would be interested in a counterexample
- saagarjha 7y agoI think the current outlook on this is "the only reason we're not seeing speculative bugs with AMD is because nobody is looking and they're probably more annoying to find", not that they're not there.
- deleted 7y ago[deleted]
- paulmd 7y agothe new AMD attack effectively breaks KASLR (the "metadata" that the attack reveals is page table layouts) and AMD has announced they're not going to patch it. itself it's not a problem but if you pair it with something else it destroys a major line of defense against that something else. AMD is still architecturally vulnerable to some variants of SPECTRE, they just consider it "hard to exploit", but they do recommend you run KASLR to harden against it. Well, so much for that.
- AnthonyMouse 7y agoWasn't KASLR (really KPTI, originally a KASLR hardening technique) a mitigation against Meltdown, which AMD isn't vulnerable to, rather than Spectre?
- chousuke 7y agoAs far as I understand it, KASLR is a general hardening technique to shuffle the kernel address space so that it's harder for attackers to use vulnerabilities successfully to attack the kernel. I don't think it's specifically for Meltdown.
- AnthonyMouse 7y agoASLR is a general technique to try to prevent memory corruption vulnerabilities from being turned into code execution when the attacker can determine the location of already-existing code in memory and use the memory corruption to cause program flow to jump to it. It works pretty well against remote code execution because it's hard for an attacker who can't already execute arbitrary code on your machine to determine the address space layout. In principle it can also be used to protect the kernel against user processes, but that's much harder because a process that can already execute arbitrary user code on the same machine can use a variety of side channel attacks like this to determine the kernel address space layout. KPTI was originally proposed to close some of those side channels, but it's kind of expensive. It only got enabled by default (on Intel) because it also mitigates Meltdown, which is a much worse problem. It also doesn't handle all of the side channels: http://www.cs.ucr.edu/~nael/pubs/micro16.pdf http://www.cs.ucr.edu/~nael/pubs/micro16.pdf Meanwhile, if some kernel code is vulnerable to Spectre (i.e. the Spectre mitigations are not implemented properly), it could allow the attacker to read arbitrary kernel memory. That is obviously very bad, but the ability to read arbitrary kernel memory implies that the attacker can already determine the kernel address space layout, so I'm not sure how KASLR would be helpful in mitigating that.
- avianes 7y ago> The "new" AMD attack depends on lack of already existing spectre mitigations. No, it's a misunderstanding to say that the flaw in the "Take A Way" whitepaper depends on a mechanism already patched. Attack scenarios which are used in the paper to show the feasibility of the 2 new side channels are patched (except the KASLR entropy reduction), but the side-channels themselves are not patched.
- kllrnohj 7y ago> but the side-channels themselves are not patched. And might never be patched just like FLUSH+RELOAD never was. And the paper itself even points out that FLUSH+RELOAD is a more applicable attack than Load+Reload is: > Comparison with Flush+Reload. While Flush+Reload invalidates a cache line from the entire cache hierarchy, Load+Reload only evicts the data for the sibling thread from the L1D. Thus, Load+Reload is limited to cross-thread scenarios, while Flush+Reload is applicable to cross-core scenarios too. Collide+Probe is more interesting as it can use virtual address instead of physical address in comparison to Prime+Probe. That may get a microcode update to do a way flush on context switch as part of general Spectre mitigations (just like the branch predictors are), but it can also be handled entirely in software by adjusting how the AES implementation works as the paper also talks about. But fundamentally what these attacks enable are super old & well known, with multiple existing mechanisms that fulfill similar roles. It's why Spectre/Meltdown never focused on the side-channel part of the attack, because it seems to just be assumed side-channels will always exist. And why the paper used existing, documented vulnerabilities to do the exploit side of their PoC, just changing the side-channel used to ex-filtrate the data. Is there something particularly unique or severe about "Take A Way" other than techchrunch's bad reporting of it?
- avianes 7y ago> But fundamentally what these attacks enable are super old & well known, with multiple existing mechanisms that fulfill similar roles. It still has to be published. The article doesn't claim to break all the isolation mechanisms of the processor like Spectre/Meltdown. Why should we compare this paper with Spectre/Meltdown? > Is there something particularly unique or severe about "Take A Way" other than techchrunch's bad reporting of it? Yes, there are at least three things in "Take A Way" which is interesting: - These side-channels are harder to detect because it doesn't require a very intensive use of the cache (no flush / filling all cache ways / etc.). A single collision is enough to evict a targeted cache line. - It allows to set up a covert channel that can transfer up to 588.9 kB/s. - They did a reverse engineering job on a processor mechanism and its undocumented hash function.
- makomk 7y agoIt's a cache-based timing sidechannel attack that leaks the address of memory accesses. In general, you should probably assume that every CPU with caches is susceptible to those (so every one with reasonable performance). As the paper mentions, there have been other cache side channel attacks that broke cryptographic implementations and only had working exploits on Intel - people didn't count those as Intel-specific attacks along with the Meltdowns or L1TFs either then or now, though, because there was no fundamental reason why it shouldn't be possible to exploit other chips the same way. Treating this one differently and somehow comparable to Intel CPUs just outright leaking data across privilege boundaries seems like a false attempt at injecting balance where none exists.
- spectramax 7y ago“Fanboyism” needs to stop for AMD and Intel. It’s clouding facts and objectivity. These days people have a hard on for AMD as if it’s some kind of a religious messiah saving them from doom. It bothers me and I don’t really understand. There are some really vile comments about Intel and unreasonable praise for AMD - simply because it’s the “underdog”. What is this? Some kind of a sport that one is rooting for the “underdog”. It’s a multi billion dollar corporation.
- ghusbands 7y agoThe post you're replying to fairly clearly states that security issues in Intel chips are pushing them to buy AMD, next. It doesn't look at all like "fanboyism".
- spectramax 7y agoI’m just talking about the general theme of AMD/Intel discussions on HN. There is a heavy bias for AMD, not just on HN but everywhere on the internet. Just go to Anandtech forums. I should clarify that my frustration isn’t about what the OP said. It’s a general observation.
- cosmiccatnap 7y agoIts not a bias it's just true. Intel has chips that are objectively underperformannt and less secure based on everything we know currently. There are no good reasons anyone should pick an Intel chip for their desktop system for the foreseeable future.
- spectramax 7y agoWe are talking about server chips? Can you point to some comparisons?
- kllrnohj 7y ago> We are talking about server chips? What gave you that idea? This thread was clearly about someone building a local PC. There's no reason to assume that'd be a server chip? But even in the server world go look up any comparison of Epyc Rome vs. Intel Xeon and you'll still struggle to find a reason to go Intel. The Epyc 7742 is in a league of its own at this point.
- MatthiasP 7y agoThere are good reasons to go with AMD over Intel CPUs at the moment, the number of published security exploits should not be one. There is nothing fundamentally more insecure in the Skylake CPU architecture than in Zen 2, just one has more marketshare and gets scrutinized more intensely.
- kllrnohj 7y ago> There is nothing fundamentally more insecure in the Skylake CPU architecture than in Zen 2 Except there is. Hence why Skylake suffered from Meltdown while AMD didn't. Skylake's design is to do ACL checks at instruction retirement instead of up front. AMD's is the reverse. Software workarounds for Meltdown exist, yes, but the Skylake architecture still fundamentally has that insecure design.
- deleted 7y ago[deleted]