Hacker News new | ask | show | jobs
by freehunter 3041 days ago
>https://pdfs.semanticscholar.org/2209/42809262c17b6631c0f653...

Literally since 1995. There's no way Intel hasn't read this report from the NSA detailing how insecure the x86 platform is where they literally call out this exact feature as a security risk. This feature that was not accidental, but intentionally designed.

Why exactly are you blindly defending Intel, especially with such easily disprovable arguments?

2 comments

It isn't the cache side channel that is the important part of meltdown. Flush-reload is just out the information is retrived and ask acceptable problem.

The problem is data hitting the cache when it comes from an unreadable page. Meltdown looks like a bug in the cache hit logic because the page information is already in the tlb, and the fix is probably fairly trivial.

If the unreadabld page doesnt hit cache or is never mapped there in the first place, spectre can only read its own process.

Really, the "exact same feature"? None of the processors in that report even support OoOE.