Regardless of the hype around the release, the bugs are real, accurately described in their technical report (which is not public afaik), and their exploit code works.
-
-
This is the truest comment anyone has made about my week so far: https://twitter.com/wildcardNP/status/973921044170989568 …
This Tweet is unavailable.Show this thread -
AMD published an initial technical assessment of the flaws from CTS and, by all indications, it agrees with our own. They even linked to our blog post! https://community.amd.com/community/amd-corporate/blog/2018/03/20/initial-amd-technical-assessment-of-cts-labs-research …
Show this thread
End of conversation
New conversation -
-
-
Remember, these things tend to cut both ways. 'trusted computing' has a lot in common with DRM - ultimately somewhere there is a way for the owner to break the lock, because it's on his property. In the end, the only secure, trustworthy operating system is by nature open.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
These
$AMD flaws are more extreme than you think. Imagine you rent an AMD server in a cloud provider, previously managed by a hacker or somebody hacked. You are now owned permanently, leaking your data to the hacker and never noticing it. Also applies to the second hand market. -
-
- 1 more reply
New conversation -
-
-
This^ made me somewhat excited too. I'd been trying to break into the PSP of my AMD laptop, but no luck yet. Spent some time re'ing a similar ARM PSP bootloader (https://github.com/coreboot/blobs/tree/master/soc/amd/stoneyridge/PSP …). Then two week later this announcement goes out! Too bad there's so little details.
Thanks. 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.