From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wFQoqcHBu_s9 for ; Tue, 23 Aug 2011 15:39:48 +0200 (CEST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 23 Aug 2011 15:39:48 +0200 (CEST) Message-ID: <4E53AD94.5@mousecar.com> Date: Tue, 23 Aug 2011 09:39:32 -0400 From: ken MIME-Version: 1.0 References: <4E4BFE0C.3040703@mousecar.com> <4E526C56.7080202@mousecar.com> <1314030003.2065.9.camel@scapa> <4E52D93A.10802@mousecar.com> <20110823125759.GA21623@tansi.org> In-Reply-To: <20110823125759.GA21623@tansi.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] recovering forgotten passwords for 2 LVs Reply-To: gebser@mousecar.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt Cc: Arno Wagner On 08/23/2011 08:57 AM Arno Wagner wrote: > On Mon, Aug 22, 2011 at 06:33:30PM -0400, ken wrote: > [...] >> Yves, thanks for replying. >> >> This setup worked fine for years without changing anything on it. I'm >> fairly certain that there are two logical volumes on /dev/sda5, both >> encrypted. As said, when I booted the system up, I was prompted for two >> passphrases (one for each filesystem). >> >> >> Does this tell us anything? >> >> # cryptsetup luksDump /dev/sda5 >> LUKS header information for /dev/sda5 >> >> Version: 1 >> Cipher name: aes > [...] > > It does. /dev/sda5 has a LUKS container at the start with > one passphrase active. For password breaking attempts, it > does not matter that there are some LVM mappings. I advise > to just ignore any LVM stuff for the moment and to run your > password guessing attempts against /dev/sda5. > > You will possibly not get you data, but the password checking > will be good, unless that thing was created using > decrypt_derived or the like. I doubt that, as then you > should have been asked only for one password. > > Once you have the password recovered, you should be able > to do a normal boot. > > Arno Thanks! That's good news. I was specifically worried that my running "cryptsetup luksOpen /dev/sda5 name" might not be accessing what it should... and so that it would *never* succeed, even with the correct passphrase. Once I determine the correct passphrase (big hopes... I've already tried a lot of them), I can take the drive out of the enclosure and install it back in its original machine. It should then boot properly. (This is Plan A anyway.) :) Best regards to all, ken -- War is a failure of the imagination. --William Blake