Return-Path: Received: from mail01.freesources.org (mx01.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 ; Tue, 1 Sep 2009 11:34:31 +0200 (CEST) Date: Tue, 1 Sep 2009 11:34:26 +0200 From: Jonas Meurer Message-ID: <20090901093425.GD6333@resivo.wgnet.de> References: <4A9B01E1.5030205@tiscali.it> <20090901011335.GC22049@resivo.wgnet.de> <4A9CE6B0.1070702@tiscali.it> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CblX+4bnyfN0pR09" Content-Disposition: inline In-Reply-To: <4A9CE6B0.1070702@tiscali.it> Subject: Re: [dm-crypt] Help: after crypttab modify > begin: waiting for root file system List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Tommaso Cc: dm-crypt@saout.de --CblX+4bnyfN0pR09 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable hey again, On 01/09/2009 Tommaso wrote: > Thank you for your reply :) I already managed to rescue my system and > undo my changes using the initrd.imgXXX.bak as you said (phew! :) ), > however I still have a couple of problems, one of which is really WEIRD... >=20 > The first problem is that I still can't manage how to use the cleartext > key_temp on /boot to automatically start the system without requesting a > passphrase. However thank you for pointing me at the passdev script, I > didn't know that, suppose it's intended also for this, I'll give a look > at that as soon as possible. yes, that's exactly what passdev is meant for. > The second, weird problem is the following. Being unable to use the > keyfile for the automount, I temporarily added a second passphrase slot > to the above device. So now, when at boot a passphrase is requested, you > can insert either passphrase1 (the old one) or passphrase2 (the new one, > which is known also by other trusted people who should so be able to > reboot the system in my absence). > The WEIRD problem now is: if I insert passphrase1 the system starts > normally and all is good. If I insert passphrase2... the passphrase is > accepted, the disk is unlocked, the system starts... and all works > EXCEPT for the network card o.O It hangs up on DHCPREQUEST and after a > minute or so it says: >=20 > eth1: device is not ready >=20 > I'm really unable to understand why the two issues (the different > passphrase and the eth1 not ready) should be related... but I succeeded > in reproducing this behaviour many times and I'm pretty sure it depends > on the passphrase... that really sounds weird. if the unlocked device _is_ the same for both passphrases, then it will behave similar. thus i don't see how issues with network should be related to the used keyslot. greetings, jonas --CblX+4bnyfN0pR09 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqc6qEACgkQd6lUs+JfIQJiBwCgilNsMEMetLxfx8sr3TNiaLyM QfEAn2tfTFKmj4uCjjOX+SmE8DMM3l1o =4i7G -----END PGP SIGNATURE----- --CblX+4bnyfN0pR09--