diff --git a/content/notes/intel-me-rootkits.md b/content/notes/intel-me-rootkits.md index 9bc24c0..e17a636 100644 --- a/content/notes/intel-me-rootkits.md +++ b/content/notes/intel-me-rootkits.md @@ -5,9 +5,9 @@ replyURI: "https://mastodon.social/@byterhymer/109181969125151465" replyTitle: "Don't forget there have already been Intel ME rootkits too" replyType: "SocialMediaPosting" replyAuthor: "@byterhymer@mastodon.social" -replyAuthorURI: "https://mastodon.social/@byterhymer/109181969125151465" +replyAuthorURI: "https://mastodon.social/@byterhymer" --- -I know of two Intel ME rootkits that didn't involve Intel AMT; the latter can be enabled/disabled on "vPro" chips. One rootkit was from 2009 and seems less relevant now; the more recent of the two was by {{. +I know of two Intel ME rootkits that didn't involve Intel AMT; the latter can be enabled/disabled on "vPro" chips. One rootkit was from 2009 and seems less relevant now; the more recent of the two was by {{. Without AMT, they required physical access. Most PCs are woefully unprepared against the sorts of attacks enabled by physical access, and ME is only one entry in a long list of issues.