Discussion in 'The Guru's Pub' started by StewieTech, Sep 3, 2018.
This is a silly thread.
Welcome to the society of Anonymous Attention Whores!
(How do you like AAW abbreviation guys?)
Bourbon Barrel PC
That is beautiful.
Especially the bottle inside the case.
I like that Zipcy
MUHAHAHAHAHAHA, yet another bug, yet another Intel one and yet another one which doesnt bother AMD if I read this correctly:
Access to everything, the golden key. Ladies and gentlemen: Intel has it.
Imo, it is easier to kidnap a family member to know "victim"`s secrets than to use the method described.
Also, are you sure you wanted to post it here?
Probably he just wanted to have a like
TBH: the fail thread doesn't give you as much likes as posting it here.
@mbk1969 : it's still one which may get abused by using other intrusion vectors and then using this to get data exfiltrated. I mean ... you can almost choose what you want and it's an Intel "feature", included in every CPU, so enabled by (de-)fault in a lot of devices.
But to be fair: The same could happen with AMD. I don't want to do Intel-only bashing. Both have their flaws and I bet there are some 0-dayz for both already available for some secret service. Like the NSA toolkit showed us already ...
I think, you got it "choose what you want" a bit wrong. Imo they only mean choose what chunk of cache memory to read - and that is far from "choose what you want" to read.
Btw, after reading their sheet two thoughts came to me:
1 - all these side channel vulnerabilities are about cache memory.
2 - hence there is very simple solution to get rid of sensitive information in cache memory - archive some binary file (video or just trash) with size bigger than cache and - voila! - most of the cache is loaded with content of that archive file.
Putting this in the cache: