All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Decrypting a drive; says a correct password is "incorrect"
Date: Fri, 6 Jan 2017 09:57:49 -0600	[thread overview]
Message-ID: <o4oepp$un$1@blaine.gmane.org> (raw)
In-Reply-To: <CAOoEu4SeRCV5Wurwu7bg2tbxtGSzOPyNB746q1dYXUufK-7zpw@mail.gmail.com>

On 01/04/2017 08:34 PM, K Mmmm wrote:
> Using a platter switch, I was able to copy most of the data to a new
> hard disk. Fortunately, *there _does_ appear to be a valid version
> of /_a_ /LUKS header still intact.* However, the password I was
> using isn't working.

Did "most of the data" include the entire ~2MB LUKS header? You need at least the first 256KB to get all the stripes of the first keyslot. If that data is not all bit-for-bit perfect, the master key cannot be recovered and your data cannot be decrypted. You can look at section 4.2 of the cryptsetup FAQ at <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions#4-troubleshooting> for information on how to build and run a keyslot checker that can test for obvious damage to the keyslots ("obvious" meaning "data with low entropy appearing in places that should appear random").

> I think the partition layout might be relevant, as there is only a 2
> space between the EXT and Linux partitions.

Your partition layout is fine. Logical partitions (numbers 5 and higher) exist within the extended partition. All that is needed is space for the 1-sector extended partition header before the start of partition 5.

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.

  reply	other threads:[~2017-01-06 15:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05  2:34 [dm-crypt] Decrypting a drive; says a correct password is "incorrect" K Mmmm
2017-01-06 15:57 ` Robert Nichols [this message]
2017-01-10  8:47 ` K Mmmm
2017-01-10  9:06   ` Sven Eschenberg
2017-01-10  9:22     ` Arno Wagner
2017-01-10 10:23       ` Sven Eschenberg
2017-01-10 13:58         ` Arno Wagner
2017-01-10  9:18   ` Arno Wagner
2017-01-10 15:43   ` Robert Nichols
2017-01-11  1:47     ` Arno Wagner
2017-01-11  2:17       ` Robert Nichols
  -- strict thread matches above, loose matches on Subject: below --
2017-01-05 16:22 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='o4oepp$un$1@blaine.gmane.org' \
    --to=rnicholsnospam@comcast.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.