DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ken <gebser@mousecar.com>
To: dm-crypt <dm-crypt@saout.de>
Cc: Arno Wagner <arno@wagner.name>
Subject: Re: [dm-crypt] recovering forgotten passwords for 2 LVs
Date: Tue, 23 Aug 2011 09:39:32 -0400	[thread overview]
Message-ID: <4E53AD94.5@mousecar.com> (raw)
In-Reply-To: <20110823125759.GA21623@tansi.org>

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

  reply	other threads:[~2011-08-23 13:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17 17:44 [dm-crypt] recovering forgotten password ken
2011-08-17 19:35 ` Arno Wagner
2011-08-17 19:40   ` Arno Wagner
2011-08-22 14:48 ` [dm-crypt] recovering forgotten passwords for 2 LVs ken
2011-08-22 16:19   ` Yves-Alexis Perez
2011-08-22 22:33     ` ken
2011-08-22 22:53       ` Milan Broz
2011-08-23  0:23         ` ken
2011-08-23  7:43           ` Yves-Alexis Perez
2011-08-23  9:35             ` ken
2011-08-23 11:59         ` ken
2011-08-23 12:57       ` Arno Wagner
2011-08-23 13:39         ` ken [this message]
2011-08-22 17:16   ` Arno Wagner
2011-08-23 13:17     ` ken
2011-08-23 13:47       ` Arno Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E53AD94.5@mousecar.com \
    --to=gebser@mousecar.com \
    --cc=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox