From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] [No key available with this passphrase.]
Date: Thu, 11 Aug 2016 01:01:05 +0200 [thread overview]
Message-ID: <20160810230105.GA17901@tansi.org> (raw)
In-Reply-To: <CABs20cDcAjpDKtB+NrJWRP==4z946NV3f36V4srfAK=3c3hLMw@mail.gmail.com>
Well, your keyslot looks intact. If you really have no
non-ascii elements in the key and you are using the rigth
passphrase, then we have exhausted all the easy things.
So is there anything else that may have changed?
Keyboard-map? A password-change that went wrong?
Regards,
Arno
On Wed, Aug 10, 2016 at 21:22:20 CEST, Valentin Buza wrote:
> I forgot to add: The key has 16 characters and none is non-ASCII.
>
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2016-08-10 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 19:22 [dm-crypt] [No key available with this passphrase.] Valentin Buza
2016-08-10 23:01 ` Arno Wagner [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-10 19:16 Valentin Buza
2016-08-10 13:27 Valentin Buza
2016-08-10 16:03 ` Arno Wagner
2016-08-10 12:01 Cristian-Valentin BUZ?
2016-08-10 12:43 ` 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=20160810230105.GA17901@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.