From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: [dm-crypt] Re2: No key available for this passphrase
Date: Sun, 9 Sep 2012 01:16:14 +0200 [thread overview]
Message-ID: <20120908231614.GA4430@tansi.org> (raw)
In-Reply-To: <d3ab01d24791ac5db88dc3a434024018@tenak.net>
You also should probably look at the key-encoding angle further.
It is not quite as simple as it seems, see FAQ item 1.2,
"PASSPHRASE CHARACTER SET". The problem is that not only
may your keymap change after some updates and you end up
inputting the wrong characters, you may also enter the
same characters (visible), but theior encoding has changed.
Your one successful mapping after update may not be
as good as it seems. If you enter the passphrase before
the encoding is set, but after that the system changes
the encoding for password entry (something to it may do on
first boot after update...), you could enter your passphrase
once, it works, but then the system changes it and it does
not work again.
The thing is that all except the 94 printable characters from
http://en.wikipedia.org/wiki/ASCII
change their encoding when the system is updated to use
UTF-8. Cryptestup reads the passphrase in binary and the
characters not in ASCII 7-bit will look different to it.
Your header and keyslot looks fine, we have this one
successful unlock, but not additional ones. This makes
me kind of suspicuous.
So:
- Do you have any characters in your passphrase that are
not in the table on http://en.wikipedia.org/wiki/ASCII?
- Has the system possibly changed the character encoding?
- Did the second system you tried the unlock on already have
the update you did on the first system?
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2012-09-08 23:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 9:03 [dm-crypt] No key available for this passphrase Marcos
2012-09-08 13:35 ` Arno Wagner
2012-09-08 18:47 ` Marcos
2012-09-08 20:02 ` Arno Wagner
2012-09-08 20:51 ` Marcos
2012-09-08 22:47 ` Arno Wagner
2012-09-09 12:53 ` Marcos
2012-09-09 13:49 ` Arno Wagner
2012-09-09 14:06 ` Marcos
2012-09-08 23:16 ` Arno Wagner [this message]
2012-09-09 12:58 ` [dm-crypt] Re2: " Marcos
2012-09-08 22:45 ` [dm-crypt] " Matthias Schniedermeyer
2012-09-09 8:45 ` Milan Broz
2012-09-09 13:42 ` 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=20120908231614.GA4430@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox