|
|||||||||||
|
Re: full drive encryption - check /boot for manipulation
From: Michel Messerschmidt <lists(at)michel-messerschmidt.de>
Date: Thu Oct 18 2007 - 17:29:13 EDT
Filesystem encryption does *not* protect against trojan horses and similar kind of malware. It serves other purposes, for example prevention of offline attacks and data leakage. In theory, any file in use in the running system (and therefore unencrypted) can be targeted by a trojan horse. Even if you are able to encrypt the boot partition what about the code in the MBR? If you are concerned about the physical security of a system you can't solve it just with software. Rather look for access restrictions to the hardware, chassis lock and intrusion sensors, disabled alternative boot methods, restrictions on BIOS and bottloader level. > It simply checks the md5sum of all files in /boot and if there are new or vanished files. This is better achieved with integrity checkers like aide or tripwire. Note that the difficult task is not to create the checksums but to store it in a secure but accessible location.
Even an integrity check during kernel boot is no help to ensure a
trusted boot process (consider virtualization attacks at the bios/boot
loader level).
Michel -- To UNSUBSCRIBE, email to debian-security-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Thu Oct 18 17:29:49 2007 This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 06:54:13 EDT |
||||||||||
|
|||||||||||