3 ms·
I don't think it's relevant to the article. If your host machine has malware in CPU firmware, then it doesn't matter whether you boot from [stateless] USB, beca
by deepsun 8y ago
I don't think it's relevant to the article. If your host machine has malware in CPU firmware, then it doesn't matter whether you boot from [stateless] USB, because malware sits between your kernel and, say, keyboard, network card, or display.
- justifier 8y agosounds horrifying can you point to any resources on a few things: (o) examples of these kinds of malware, either code or writeups (i) ways of detecting these kinds of malware (ii) ways of removing these kinds of malware (iii) ways of preventing these kinds of malware from getting installed
- efp 8y agohttps://www.archive.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf https://www.archive.ece.cmu.edu/~ganger/712.fall02/papers/p7... http://spritesmods.com/?art=hddhack&page=5 http://spritesmods.com/?art=hddhack&page=5 https://blog.invisiblethings.org/papers/2015/x86_harmful.pdf https://blog.invisiblethings.org/papers/2015/x86_harmful.pdf
- justifier 8y agoit looks like all of your links are basically only addressing my initial list item the first link is about modifying a system's c compiler which the op's tails live usb is infact a solution to the second is about altering firmware on harddrives, which is an engrossing writeup, thank you, but does fall short of suggesting ways to identify and remedy such an invasion your third one is about intel's ME which i figured i'd see someone link to unfortunately, the really interesting listed elements in my original post are the preventative and resolutive elements