Ha. Who needs Meltdown when the Windows 7 kernel just gave every userspace process writable page tables? "Oops." http://blog.frizk.net/2018/03/total-meltdown.html …
-
-
Replying to @marcan42
Worth pointing out the note at the end, that he discovered it after it had already been patched. It's pretty freaking bad, yeah, but its not like it was being exploited in the wild before fix, which is always a good thing to remember.
1 reply 0 retweets 2 likes -
Replying to @hedgeberg
This is one of those cases where the important thing is not the actual problem (which is pretty bad in and of itself) but *how* it happened. There's clearly a QA failure here at some point.
1 reply 0 retweets 2 likes -
Replying to @marcan42
Oh yeah, no doubt, but on the bright side it was also self-caught, which is a plus for MS's red team, at least? Idk, this was a major flaw and I'm just trying to let myself pretend there's some good in the horror :/
1 reply 0 retweets 0 likes -
Replying to @hedgeberg
To their credit, they didn't immediately start blocking anyone who pointed it out or liked a tweet pointing it out (yes, shots fired).
1 reply 0 retweets 2 likes -
Replying to @marcan42
...Shots fired at /who/?? I feel like I'm missing a hell of a story here.
1 reply 0 retweets 1 like
Oh, just that time Spender got so mad at me he threw a blockfest, then ragequit Twitter. It was so sad it made it to The Register. https://www.theregister.co.uk/2016/04/27/linux_security_bug_report_row/ … (obligatory clarification: this wasn't an unexpected 0day disclosure; their policy was to take these bugs as public reports)
-
-
Replying to @marcan42
Oh right I remember you posting this, but I had no idea any of the fallout happened. That's fucking amazing.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.