Return-Path: Received: from mail01.freesources.org (mail01.freesources.org [80.237.252.149]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Mon, 21 Sep 2009 16:10:30 +0200 (CEST) Received: from dslb-088-068-056-034.pools.arcor-ip.net ([88.68.56.34] helo=resivo.wgnet.de) by mail01.freesources.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1Mpjb2-0005T9-S3 for dm-crypt@saout.de; Mon, 21 Sep 2009 14:10:30 +0000 Received: from resivo by resivo.wgnet.de with local (Exim 4.69) (envelope-from ) id 1Mpjb2-0007u6-0j for dm-crypt@saout.de; Mon, 21 Sep 2009 16:10:28 +0200 Date: Mon, 21 Sep 2009 16:10:27 +0200 From: Jonas Meurer Message-ID: <20090921141027.GD11909@resivo.wgnet.de> References: <20090917215809.GC23460@resivo.wgnet.de> <2894495.33731253540870681.JavaMail.root@IRL-DUB-P-SRV-02> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XvKFcGCOAo53UbWW" Content-Disposition: inline In-Reply-To: <2894495.33731253540870681.JavaMail.root@IRL-DUB-P-SRV-02> Subject: Re: [dm-crypt] Remote authentication? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de --XvKFcGCOAo53UbWW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 21/09/2009 Niall Murphy wrote: > ----- Jonas Meurer wrote: > > it depends on whether you want to encrypt the whole system, including > > root filesystem, or if encrypting the data partitions is enough. > >=20 > > for the latter case you can ssh-login into the machine after boot, > > unlock the encrypted data partitions and start services manually. > >=20 > > in case that the root partition should be encrypted, you'll need to > > start a minimal ssh daemon in the initramfs in order to login remotely > > and unlock the root partition before the root filesystem is mounted. > >=20 > > the debian cryptsetup package supports remote unlocking of the root > > partition with the help of a dropbear ssh server inside the initramfs. > > see README.remote for more information: > > http://svn.debian.org/wsvn/pkg-cryptsetup/cryptsetup/trunk/debian/READM= E.remote > >=20 > > please note that this information is specific to the debian and ubuntu > > distributions. it doesn't apply if you use any other linux distribution. > >=20 > Thanks Jonas, >=20 > That sounds ideal. However, i came across this so have some reservations. > http://www.howtoforge.com/unlock-a-luks-encrypted-root-partition-via-ssh-= on-ubuntu >=20 > It lists two types of attack to this approach: >=20 > (1) ColdBoot Attack by reading the crypto password from the ram blocks > (not much you can't do against that without special hardware, see > here) this attack is possible against all kinds of disk encrpyption and in no way related to remote disk encryption. > (2) The created initrd can be manipulated so that it logs the crypto > password somewhere. As /boot is not encrypted an attacker may gain > this way the password for the LUKS-devices. You could, to prevent > that, make a bootable cd with the according kernels and initrds and > implement some kind of hash check... maybe there are other methods... > feedback is welcomed here. yes, unencrypted boot partition is a security issue, but then an attacker as well can modify the kernel. attackers don't even have to modify software, they could install additional hardware like keyloggers as well.=20 in general you can only trust your system if you've physical control over it. this again is not related/limited to remote disk encryption. greetings, jonas --XvKFcGCOAo53UbWW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkq3iVMACgkQd6lUs+JfIQJYqwCfQEUdqZDAxjB4UrfQoLTGalBf TCoAn2XaKHVviqxmHtcolsV3iwDk1Mt3 =GhAc -----END PGP SIGNATURE----- --XvKFcGCOAo53UbWW--