SoylentNews is people
SoylentNews
SoylentNews first reported the vulnerabilities on January 3. Since then, we have had a few stories addressing different reports about these vulnerabilities. Now that it is over two weeks later and we are *still* dealing with reboots, I am curious as to what our community's experience has been.
What steps have you taken, if any, to deal with these reports? Be utterly proactive and install every next thing that comes along? Do a constrained roll out to test a system or two before pushing out to other systems? Wait for the dust to settle before taking any steps?
What providers (system/os/motherboard/chip) have been especially helpful... or non-helpful? How has their response affected your view of that company?
What resources have you been using to check on the status of fixes for your systems? Have you found a site that stands above the others in timeliness and accuracy?
How has this affected your purchasing plans... and your expectations on what you could get for selling your old system? Are you now holding off on purchasing something new?
(Score: 0) by Anonymous Coward on Sunday January 21 2018, @06:39AM
I was actually referring to the exploit code, not the patch checker.
So i used this:
https://github.com/paboldin/meltdown-exploit [github.com]
When I run on a P4 prescott 630, I have to run the exploit code somewhere between 200 and 2000 times to get it to show the correct "stolen" data and even then, not all bytes are correct. So my conclusion is that P4s of that vintage theoretically have the vulnerability, but its not reliable enough to steal much data.
I ran using the same linux live USB key on different machines with the same exact 32 bit executable. To verify that the executable could work, I ran it on an Intel i5-2520M and it showed the vulnerability every time for about 30 runs (all "stolen" bytes correct).
The link above also has lists of VULNERABLE and NOT VULNERABLE cpus -- see the issues 19 and 22.