The Reuters article quote Intel's blog: "...this further underscores the need for everyone to adhere to security best practices," the company said in a blog post.
That first best practice would be not buying Intel chips. Glad there's an alternative.
No doubt Intel found out that someone else was going to disclose these flaws, so they got out ahead of it. They're pulling a Rudy here; try to beat the scandal, but then create one with their attempt to deflect responsibility to someone else:
"We are not aware of reports that any of these methods have been used in real-world exploits, but this further underscores the need for everyone to adhere to security best practices,"
Yeah, Intel. Everyone. Including the folks who have done the worst job of adhering to
Today's Wired article [wired.com] says the details of the Foreshadow attack [foreshadowattack.eu] would be presented tomorrow. Somebody is coordinating all this.
Intel followed the very successful Pentium 3 design with Netburst, a radical new architecture that used a VERY long pipeline in the chase for a 10GHz (eventually) clock. It was terrible, but Intel paid outlets at the time, like Slashdot, to promote it as the second coming of chr-st.
Meanwhile AMD was using its newly aquired team of CPU architects to build the world's first 64-bit compatible x86 chip, and the world's first true dual core x64 chip. And it was fantastic.
Intel could have had a monopoly if they didn't make the Pentium bug math error.
Computers are supposed to be "perfect" at computations, but the Intel bug threw some court cases in the wrong direction. I'm not sure they can be trusted anymore.
Good lord, you can't be serious. The road to silicon nirvana is paved with errata sheets. (And always has been.)
Furthermore, the division bug is a terrible example to bolster your cause, because the algorithm was correct in the first place, and the implementation of the
The Reuters article quote Intel's blog: "...this further underscores the need for everyone to adhere to security best practices," the company said in a blog post.
That first best practice would be not buying Intel chips. Glad there's an alternative.
No doubt Intel found out that someone else was going to disclose these flaws, so they got out ahead of it. They're pulling a Rudy here; try to beat the scandal, but then create one with their attempt to deflect responsibility to someone else:
Yeah, Intel. Everyone. Including the folks who have done the worst job of adhering to
Today's Wired article [wired.com] says the details of the Foreshadow attack [foreshadowattack.eu] would be presented tomorrow. Somebody is coordinating all this.
A brief history...
Intel followed the very successful Pentium 3 design with Netburst, a radical new architecture that used a VERY long pipeline in the chase for a 10GHz (eventually) clock. It was terrible, but Intel paid outlets at the time, like Slashdot, to promote it as the second coming of chr-st.
Meanwhile AMD was using its newly aquired team of CPU architects to build the world's first 64-bit compatible x86 chip, and the world's first true dual core x64 chip. And it was fantastic.
No matter how much lies
Good lord, you can't be serious. The road to silicon nirvana is paved with errata sheets. (And always has been.)
Furthermore, the division bug is a terrible example to bolster your cause, because the algorithm was correct in the first place, and the implementation of the