From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OA5yo-00042u-HU for garchives@archives.gentoo.org; Thu, 06 May 2010 18:39:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C04C5E0809; Thu, 6 May 2010 18:38:45 +0000 (UTC) Received: from zion.lichtfels.com (zion.lichtfels.com [88.198.33.170]) by pigeon.gentoo.org (Postfix) with ESMTP id 73E10E0809 for ; Thu, 6 May 2010 18:38:45 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zion.lichtfels.com (Postfix) with ESMTP id 77EA0184019 for ; Thu, 6 May 2010 20:38:44 +0200 (CEST) Received: from zion.lichtfels.com ([127.0.0.1]) by localhost (zion [127.0.0.1]) (amavisd-maia, port 10024) with LMTP id 06693-10 for ; Thu, 6 May 2010 20:38:43 +0200 (CEST) Received: from [172.32.99.12] (mail.oops.co.at [213.129.238.225]) by zion.lichtfels.com (Postfix) with ESMTPA id 4DD0C18400B for ; Thu, 6 May 2010 20:38:43 +0200 (CEST) Message-ID: <4BE30CB2.4020307@xunil.at> Date: Thu, 06 May 2010 20:38:42 +0200 From: "Stefan G. Weichinger" Organization: oops! User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100410 Lightning/1.0b2pre Thunderbird/3.0.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Kernel upgrade and now LUKS failure. References: <4BDFF195.9070404@xunil.at> <4BE05BA3.1000509@xunil.at> <4BE07570.7020305@xunil.at> <4BE090A5.9080804@admin-box.com> <4BE0F71D.7080907@xunil.at> <4BE125AB.1030105@admin-box.com> <4BE12F73.2080708@xunil.at> <4BE1C969.1010009@admin-box.com> <4BE1D26D.1050402@xunil.at> <4BE1D3CC.9040503@xunil.at> <4BE2ED48.4090006@admin-box.com> In-Reply-To: <4BE2ED48.4090006@admin-box.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-maia at lichtfels.com X-Archives-Salt: 214eb580-d9ea-4dda-926a-c2d4286cedb1 X-Archives-Hash: e51d1ce70280048c982b39251de34324 Am 06.05.2010 18:24, schrieb Daniel Troeder: > On 05/05/2010 10:23 PM, Stefan G. Weichinger wrote: >> Am 05.05.2010 22:17, schrieb Stefan G. Weichinger: >> >>> Remember that I said: "I am not sure which HOWTO I followed" ? >>> >>> What if I didn't use aes-256-ecb? > You don't need to supplay that information to cryptsetup, it can > (should) autodetect it. To see that info for yourself run: > $ cryptsetup luksDump /dev/mapper/VG01-crypthome But I always did when I followed your example. Anyway, this part is solved now. >> Yep. See pam_mount.conf.xml: >> It's "aes-256-cbc" in my case. >> >> I was now able to luksOpen and I have the decrypted device mounted. > Hooray :) Yes :-) Currently I run an unencrypted home on another LV. >> Nice. >> >> So: >> >> the user-pw didn't change and the keyfile is OK. >> >> So why is pam_mount unable to mount it? >> >> I will now pull another backup and check/add fallback keys ;-) > There are interesting options in the cryptsetup-man page: > luksHeaderBackup and luksHeaderRestore... I think I'll add that to my > backup scripts :) Good idea. The main question is still unanswered: Why does pam_mount not work anymore with the given device/key ? Should I file a bug? S