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: Wed, 10 Aug 2016 14:43:39 +0200	[thread overview]
Message-ID: <20160810124338.GA13188@tansi.org> (raw)
In-Reply-To: <HE1PR0101MB25722C644BCDC9B949FEB0C7C51D0@HE1PR0101MB2572.eurprd01.prod.exchangelabs.com>

Hi Vali,

the first thing is to make a header-backup if you do not alredy 
have one. It is too easy to do damage when experimenting in such a
situation. Instructions are in FAQ Item 6.2 here:
https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions

That said, cryptsetup should complain on a defective header, so 
that does not seem to be it. It could be a defective keyslot though,
or still some other problem with the passphrase entry. Especially
on updates non ISO-7bit (i.e. 7 bit ASCII) chars can cause problems.

In the cryptsetup source package, you find the keyslot-checker
in misc/keyslot_checker/. Install as described in the README and check
your keyslots for obvious problems. Next steps depend on the result.

Regards,
Arno 

On Wed, Aug 10, 2016 at 14:01:11 CEST, Cristian-Valentin BUZ? wrote:
>    Hi all,
> 
>    I have a Linux Mint with full disk encryption (one big partition). For
>    the last couple of days (~ 5 days) I did not shutdown the laptop and
>    only closed the lid. Today I had a restart (probably updates were
>    downloaded in the meantime) and my passphrase does not work anymore. I
>    tried to debug with an ubuntu live usb.
> 
>    here are the commands that i've tried so far:
> 
>    [1]http://pastebin.com/Tu2fQfN2
> 
>    I've also tried with LANG=C and LANG=en_US.
> 
>    I've tried from a script:
> 
>    echo -n 'xxx' | iconv -f utf-8 -t us-ascii | cryptsetup luksOpen
>    /dev/sda3 sda3_crypt
> 
>    I've tried a script to brute force the passphrase (I am desperate and
>    maybe I've suddenly forgot the passphrase after 8 months of writing it
>    almost every day). I've tried to brute force the values of the keys
>    that I press (I still remember how I press the keys mechanically).
> 
>    What do you guys suggest to try now? Do you think that the header is
>    damaged?
> 
>    Thx,
> 
>    Vali
> 
> References
> 
>    1. http://pastebin.com/Tu2fQfN2

> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt


-- 
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
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  reply	other threads:[~2016-08-10 12:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 12:01 [dm-crypt] [No key available with this passphrase.] Cristian-Valentin BUZ?
2016-08-10 12:43 ` Arno Wagner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-10 19:22 Valentin Buza
2016-08-10 23:01 ` Arno Wagner
2016-08-10 19:16 Valentin Buza
2016-08-10 13:27 Valentin Buza
2016-08-10 16:03 ` Arno Wagner
2013-12-27  2:25 [dm-crypt] "No key available with this passphrase." Mihail Dumitrescu
2013-12-27  6:41 ` Heinz Diehl
2013-12-27 12:54 ` 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=20160810124338.GA13188@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.