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 1OAJJr-00062V-Gn for garchives@archives.gentoo.org; Fri, 07 May 2010 08:54:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 16984E06D8; Fri, 7 May 2010 08:53:47 +0000 (UTC) Received: from zion.lichtfels.com (zion.lichtfels.com [88.198.33.170]) by pigeon.gentoo.org (Postfix) with ESMTP id D92D3E06D8 for ; Fri, 7 May 2010 08:53:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zion.lichtfels.com (Postfix) with ESMTP id 912D1184022; Fri, 7 May 2010 10:53:45 +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 14482-07; Fri, 7 May 2010 10:53:44 +0200 (CEST) Received: from [172.32.99.12] (mail.oops.co.at [213.129.238.225]) by zion.lichtfels.com (Postfix) with ESMTPA id 33481184004; Fri, 7 May 2010 10:53:44 +0200 (CEST) Message-ID: <4BE3D517.8060004@xunil.at> Date: Fri, 07 May 2010 10:53:43 +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 CC: Daniel Troeder 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> <4BE30CB2.4020307@xunil.at> In-Reply-To: <4BE30CB2.4020307@xunil.at> 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: bfd21269-8e3b-4409-99e2-ebc3edf72cfa X-Archives-Hash: 709d89fb53964e855dce1ddafdcb1867 Am 06.05.2010 20:38, schrieb Stefan G. Weichinger: > The main question is still unanswered: Why does pam_mount not work > anymore with the given device/key ? additional digging: I found http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528366 where the poster tries the underlying mount.crypt call. I did that as well and get: # mount.crypt -v -o fsk_cipher=aes-256-cbc,fsk_hash=md5,keyfile=/etc/security/verysekrit.key /dev/VG01/crypthome /mnt/gschwind command: 'readlink' '-fn' '/dev/VG01/crypthome' command: 'readlink' '-fn' '/mnt/gschwind' Password: mount.crypt(crypto-dmc.c:144): Using _dev_dm_0 as dmdevice name crypt_activate_by_passphrase: Operation not permitted which is in fact the error pam_mount throws up : pam_mount(mount.c:64): Errors from underlying mount program: pam_mount(mount.c:68): crypt_activate_by_passphrase: Operation not permitted Downgrade pam_mount from 2.1 to 2.0 ... same error. But it works with pam_mount 1.33 ! I don't know which old bugs I reintroduce to my system by doing this ;-) I think I am gonna file a bug for this now. Stefan