All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] No key available with this passphrase
Date: Sat, 22 Jun 2013 12:32:29 +0200	[thread overview]
Message-ID: <20130622103228.GA14272@tansi.org> (raw)
In-Reply-To: <CABFzgH8Yv-8EjVfPy+osdCHrh3JjenGuT0zO0T5fstdB=fr9Fg@mail.gmail.com>

On Sat, Jun 22, 2013 at 01:24:59PM +0800, Packets wrote:
> On Tue, Jun 11, 2013 at 2:21 AM, Milan Broz <gmazyland@gmail.com> wrote:
> 
> > To properly run locally compiled keyslot checker tool try
> >
> > cd ~/Downloads/cryptsetup-1.6.1/misc/keyslot_checker
> > sudo LD_LIBRARY_PATH="../../lib/.libs;$LD_LIBRARY_PATH"
> > ./chk_luks_keyslots /dev/sdb1
> >
> 
> Thanks Milan. Here is the output
> 
> nelson@kazekage:~/Downloads/cryptsetup-1.6.1/misc/keyslot_checker$ sudo
> LD_LIBRARY_PATH="../../lib/.libs;$LD_LIBRARY_PATH" ./chk_luks_keyslots
> /dev/sdb1
> 
> parameters (commandline and LUKS header):
>   sector size: 512
>   threshold:   0.900000
> 
> - processing keyslot 0:  start: 0x001000   end: 0x020400
>   low entropy at: 0x010000    entropy: 0.593573

Definitely header damage in Key-Slot 0.
To find out what the damage is, re-run with -v.

> - processing keyslot 1:  keyslot not in use
> - processing keyslot 2:  keyslot not in use
> - processing keyslot 3:  keyslot not in use
> - processing keyslot 4:  keyslot not in use
> - processing keyslot 5:  keyslot not in use
> - processing keyslot 6:  keyslot not in use
> - processing keyslot 7:  keyslot not in use
> 

> >From the output above, could you tell if there the header is damage? Is
> > my storage still possible to open?

In any case, you need a header backup to access your data,
this keyslot is permanently broken.

Arno
-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult.  --Tony Hoare

  reply	other threads:[~2013-06-22 10:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 15:40 [dm-crypt] No key available with this passphrase Packets
2013-06-10 15:42 ` Packets
2013-06-10 18:21   ` Milan Broz
2013-06-22  5:24     ` Packets
2013-06-22 10:32       ` Arno Wagner [this message]
2013-06-28 11:27         ` Packets
2013-06-10 20:55 ` Arno Wagner
  -- strict thread matches above, loose matches on Subject: below --
2014-06-10 16:37 Ryan Delaney
2014-06-11  3:53 ` Arno Wagner
2017-04-29 18:27 Hammad Siddiqi

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=20130622103228.GA14272@tansi.org \
    --to=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 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.