- Joined
- Feb 3, 2017
- Messages
- 3,481 (1.32/day)
Processor | R5 5600X |
---|---|
Motherboard | ASUS ROG STRIX B550-I GAMING |
Cooling | Alpenföhn Black Ridge |
Memory | 2*16GB DDR4-2666 VLP @3800 |
Video Card(s) | EVGA Geforce RTX 3080 XC3 |
Storage | 1TB Samsung 970 Pro, 2TB Intel 660p |
Display(s) | ASUS PG279Q, Eizo EV2736W |
Case | Dan Cases A4-SFX |
Power Supply | Corsair SF600 |
Mouse | Corsair Ironclaw Wireless RGB |
Keyboard | Corsair K60 |
VR HMD | HTC Vive |
What the patch does is tell CPU to clean out the valuable information from a place where hacker can access before the hacker gets to the point where he can access it.Why? Because what that patch is doing is basically screaming at the CPU "no you won´t be doing this, you are blocked, find another route". Because if the CPU does what it was programmed to, it will put valuable information on a place where a hacker can access. Wich is what meltdown is, in easy non complex words. This is not your common insecure software code that can be 100% patched. This is on the core of the CPUs!
When that information is not there, the CPU is not going to be able to read it.
No, it cannot.Even a website can mess your meltdown patch and you are open again.
What are you going back to, one of the Atoms?If you have no problems by using a CPU at that constant risk, that´s up to you. I refuse to.
For Meltdown, AMD and most of ARMs seem to be unaffected. For Spectre, here is a list:
https://forum.level1techs.com/t/list-of-cpus-most-likely-immune-to-spectre/123128
Last edited: