Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mail.saout.de (Postfix) with ESMTP for ; Mon, 28 Dec 2009 23:57:33 +0100 (CET) Date: Mon, 28 Dec 2009 23:57:33 +0100 From: Heinz Diehl Message-ID: <20091228225733.GA16466@fancy-poultry.org> References: <4B3914FB.7060008@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B3914FB.7060008@gmail.com> Subject: Re: [dm-crypt] encrypted root: prevent / detect tampering with kernel / initrd List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 28.12.2009, Olivier Sessink wrote: > I was wondering if there are some 'common' ways to prevent tampering > with the unencrypted kernel and initrd in the case of an encrypted > root filesystem? If somebody has access to your computer they could > change the initrd and kernel and make your encryption useless If anyone ever gets physical access to your machine, all bets are off. There's no way for you to proof that your machine has not been tampered with. You can have a checksum of the contents in /boot, the MBR or whatsoever, you name it. The attacker won't care and install a hardware keylogger or whatever suits best.