LTC8K6
Lifer
- Mar 10, 2004
- 28,520
- 1,575
- 126
The reboot problem is not new news, though.Intel users are in for more patching fun!
Intel Says Patches for Meltdown and Spectre are Flawed
https://www.eetimes.com/document.asp?doc_id=1332880
The reboot problem is not new news, though.Intel users are in for more patching fun!
Intel Says Patches for Meltdown and Spectre are Flawed
https://www.eetimes.com/document.asp?doc_id=1332880
It'll all come out in the wash...and there's absolutely nothing at all that I can do in any case.
Except wait to buy my next CPU.
Haswell systems (one desktop & one Xeon) report meltdown is patched and performance is "good".
Ivy Bridge reports meltdown is patched and performance is "slower", but it's not noticeable.
FX-6300 system reports meltdown is patched and performance is "good".
All report Spectre vulnerability, but I expect no help on that at all, and I don't consider it a threat for my desktop systems anyway.
Intel is clearly still working on this, so Linus isn't helping any by screeching to the press instead of working with Intel.
Intel users are in for more patching fun!
Intel Says Patches for Meltdown and Spectre are Flawed
https://www.eetimes.com/document.asp?doc_id=1332880
Don't worry, we have a guy here that is perfectly satisfied with their patches.![]()
The way I see it, Intel isn't helping anyone because their presswork has been nothing short of duplicitous. It is much better for everyone that trusted experts become more public about what is actually happening.
I expected things to smooth out with this by now, but it seems like the situation has only gotten worse, especially for Intel. But remain comforted by the fact that the press still seems largely in thrall to the information that Intel prefers. I haven't seen much secondary or even tertiary "news" out there that doesn't paint a generally darker picture for Intel's competitors, which is truly strange.
Unless there's something I missed, I'm not seeing how Linus was screeching to the press about this. He was replying to a message by a Linux Kernel Engineer at AWS who previously spent nearly a decade at Intel and who (according the the thread) has his name on some of the patches. The press might have picked up on it, but this was a conversation between industry experts.Intel is clearly still working on this, so Linus isn't helping any by screeching to the press instead of working with Intel.
It'll all come out in the wash...and there's absolutely nothing at all that I can do in any case.
Except wait to buy my next CPU.
Haswell systems (one desktop & one Xeon) report meltdown is patched and performance is "good".
Ivy Bridge reports meltdown is patched and performance is "slower", but it's not noticeable.
FX-6300 system reports meltdown is patched and performance is "good".
All report Spectre vulnerability, but I expect no help on that at all, and I don't consider it a threat for my desktop systems anyway.
What are they going to do? They aren't going to throw out the systems they just bought. There's nothing to switch to that isn't vulnerable to Spectre anyway.The problem is the infrastructure guys that run mission critical or demanding workloads that are heavily impacted by the patches. It is also these guys that generate the most revenue for Intel, not us, the enthusiasts unfortunately.
Well, they clearly have a communication problem.Not sure how outsourcing crisis communication is going to help them with anything tangible.
What are they going to do? They aren't going to throw out the systems they just bought. There's nothing to switch to that isn't vulnerable to Spectre anyway.
Perhaps they won't buy Intel if they are looking to buy at the moment?
Perhaps they can sue Intel over loss of performance, but that'd be in litigation forever with no guarantee of winning.
Does Intel guarantee performance anyway?
When would we see data that would show that Intel is losing market share over the problem, as opposed to just losing market share to Zen anyway?
Intel users are in for more patching fun!
Intel Says Patches for Meltdown and Spectre are Flawed
https://www.eetimes.com/document.asp?doc_id=1332880
At this point I'm glad my PC is so old and I will not see and BIOS fixes. And even if I did I would probably not install them. I still fails to see why this is such a huge deal for consumers. It isn't. This is an issue for virtualized servers in the cloud. Only client issue (JavaScript) was fixed in browsers.
Exploiting any of the fixes requires code to run on your machine and if a hacker can run code on your machine, then you are REDACTED either way. In the cloud however it's a huge issue because it is 100% legitimate that I rent a VM in which I can install any software I like. And said software can then spy on other VMs on the same host. There is nothing that can be done except patching OS and BIOS. But again for consumers? Hardly matters. I mean why isn't a single expert saying this?
At this point I'm glad my PC is so old and I will not see and BIOS fixes. And even if I did I would probably not install them. I still fails to see why this is such a huge deal for consumers. It isn't. This is an issue for virtualized servers in the cloud. Only client issue (JavaScript) was fixed in browsers.
Exploiting any of the fixes requires code to run on your machine and if a hacker can run code on your machine, then you are REDACTED either way. In the cloud however it's a huge issue because it is 100% legitimate that I rent a VM in which I can install any software I like. And said software can then spy on other VMs on the same host. There is nothing that can be done except patching OS and BIOS. But again for consumers? Hardly matters. I mean why isn't a single expert saying this?
This is my take as well. At least we can disable the OS fix if we want by using InSpectre. And I sure as hell will never install a UEFI update if it becomes available for my motherboard.
This is my take as well. At least we can disable the OS fix if we want by using InSpectre. And I sure as hell will never install a UEFI update if it becomes available for my motherboard.
I completely disagree. You're talking two different things. Mitigation, vs. Prevention. It's like saying if you're in a fast enough car crash you're dead either way, so why bother with seatbelts. We allow packages from different groups to run on our systems all the time. Modern computing wouldn't exist without the concept. While we can't prevent all intrusions, we can absolutely discern a difference between something that allows access to your system, vs. something that allows it to read parts of your memory that are supposed to be highly secured, breaking established boundaries inside a system and not leaving a discernable trace.
I'm not sure there is any strong argument to be made against applying security patches. Even if we'd assume that your data is (generally) useless to state sponsors.
There are for example entire communities for people renting or buying malicious services, e.g. botnets or ransomeware. And such communities and services will more than surely employ Spectre and Meltdown exploiting code in the upcoming future, which will make you a potential target.
I'm sure that having your data encrypted and held ransom or that being part of (an aggressive) botnet responsible for DDOS'ing game servers and various websites, pushing spam or forwarding questionable/illegal material is not something that you'd want to expose your self to.
Also, Meltdown and Spectre require local access to be exploited.
What makes you say that? Are you saying data center operators do not have to worry about this issue because they restrict access to their server farm?
I'm not talking about data centers, servers or anything. I am talking about end consumers like us. The chances of being targeted by an attack using Spectre or Meltdown is extremely remote, so remote that it's not worth the hassle for me to use the mitigation patches from Microsoft and Intel which affect the stability and performance of my machine.