4 ms·
Total bull. Take the filesystem offline and run Tripwire over it (assuming you did this after a fresh install). We solved this problem in the 90s. Try to keep
by _sbrk 9y ago
Total bull. Take the filesystem offline and run Tripwire over it (assuming you did this after a fresh install).
We solved this problem in the 90s. Try to keep up.
sigh
- eli 9y agoWe had BIOS based malware in the 90s too
- alasdair_ 9y agoRight. And what do you do when the filesystem comes back clean because the malware resides in some re-flashed firmware? You can almost get a pass for being condescending ("try to keep up") if you know what you are talking about, but being both condescending AND wrong just makes you look foolish.
- _sbrk 9y agoThere's your first problem, mate: Leaving firmware writable. Back in the 90s, there was a little jumper to enable the !WR line on that EERPOM. Only an idiot left it on all the time. I can be condescending because "the kids" just don't get it; I dare say the same for you.
- besselheim 9y agoThat doesn't help you if the code running outside your filesystem is compromised. For example, a backdoor implanted in the disk firmware would be virtually undetectable for the vast majority of users.