Re:iPhone update for Meltdown-Spectre: before/after performa...
by euroclydon on Wednesday January 10, 2018 @03:33PM
(#16118788)
What about using dedicated hardware and not running the patches? At attacker has to run malicious code on your server to exploit the vulns anyhow, right?
Re:iPhone update for Meltdown-Spectre: before/after performa...
by FBISurveillance on Wednesday January 10, 2018 @04:06PM
(#16119064)
I usually don't trust people. More than one have we found things improperly secured and/or exposed to the outer internet, or otherwise at risk.
We also run black-box software from third party vendors that provide compiled JAR files which is directly related to this fuss. Last thing I'd like to have is another attack vector at home.
Re:iPhone update for Meltdown-Spectre: before/after performa...
by jrochkind1 on Wednesday January 10, 2018 @03:56PM
(#16119016)
Sure, but I think that would (potentially, with the proper exploit) turn any non-root-level code-execution-able breach of your machine of a machine into a root level one, no? Maybe that's okay?
Re:iPhone update for Meltdown-Spectre: before/after performa...
by bfrog on Wednesday January 10, 2018 @02:54PM
(#16118374)
Time to switch to an Epyc host?
Re:iPhone update for Meltdown-Spectre: before/after performa...
by FBISurveillance on Wednesday January 10, 2018 @03:09PM
(#16118543)
We're actually using those new 24-core Epyc hosts for our data science pipeline (HDP/Spark cluster) and they work much better than our previous generation Xeon-based builds.
Unfortunately, with those things it takes plenty of time to re-evaluate hardware + in our case we're mostly in the cloud where Skylakes on GCP is the most we can get.
Re:iPhone update for Meltdown-Spectre: before/after performa...
by dogma1138 on Wednesday January 10, 2018 @03:19PM
(#16118643)
AMD is vulnerable to Spectre and are not fixing variant 2 because it’s “near zero risk”.
By near zero risk they mean that no one has yet reversed engineered their branch prediction which is required to effectively exploit it.
Give it sometime and the BTI patch would have to be enforced on AMD CPUs also.
Oh well, too bad, enjoying the ride.