From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Anyone know why I can't access my volumes?
Date: Tue, 10 Dec 2019 22:51:51 +0100 [thread overview]
Message-ID: <20191210215151.GA14394@tansi.org> (raw)
In-Reply-To: <mzBNweqlB_sNysdm5cyJ2pRIFw3XaElEsyID7QdDOj673lL4M4WTREBNzTjQGsBV5qDSwYIIXAsABUCK90JmZn7jzoVAfsMfXrR4Lok0aOA=@pm.me>
Thanks for the feedback. It is really important to know how
these things happen. It is a good idea to stay within the standard
ASCII char-set for passwords and passphrases. (The "special char"
requirement some people have is really, really stupid.) Then, on a
German keyboard you only have the y/z swap, and that you usually
can just test out.
If in doubt, just make it one or two chars or words longer.
Personally, I have even dropped uppercase letters.
The problem with anything outside of standard ASCII is that the
encoding is really messed up and variable. Unicode was supposed
to solve that, but for this application it made things even
worse.
Regards,
Arno
On Tue, Dec 10, 2019 at 17:34:22 CET, Philipp Rösch wrote:
> Sorry for the late late reply.
>
> It was indeed the wrong keyboard layout. Imagine that...
>
> I was about to give up when I noticed different German layout variations
> on my live disk. One of those worked. Surprise.
>
> My case seemed strange because everything looked ok and there were no
> errors anywhere, except that the volumes wouldn't unlock.
>
> PEBKC.
>
>
--
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:[~2019-12-10 21:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 21:53 [dm-crypt] Anyone know why I can't access my volumes? Philipp Rösch
2019-10-21 7:50 ` Michael Kjörling
2019-10-21 14:33 ` Philipp Rösch
2019-10-21 14:50 ` Arno Wagner
2019-10-21 14:56 ` Philipp Rösch
2019-10-24 7:26 ` Carl-Daniel Hailfinger
2019-10-24 12:34 ` Arno Wagner
2019-10-24 19:35 ` Philipp Rösch
2019-12-10 16:34 ` Philipp Rösch
2019-12-10 17:42 ` Chris Murphy
2019-12-10 20:00 ` Michael Kjörling
2019-12-10 21:18 ` Chris Murphy
2019-12-10 21:51 ` Arno Wagner [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-21 18:16 Arno Wagner
2019-10-21 18:23 ` Philipp Rösch
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=20191210215151.GA14394@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).