All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Note: Characters inadvisable in Passphrases
Date: Sat, 09 Jul 2011 00:05:11 +0200	[thread overview]
Message-ID: <4E177F17.5060303@redhat.com> (raw)
In-Reply-To: <20110708211100.GB26099@tansi.org>

On 07/08/2011 11:11 PM, Arno Wagner wrote:

> So it is highly advisable to stay within the 94 printable 
> characters on the standard, 128 character ASCII table. The
> table can e.g. be found here: http://en.wikipedia.org/wiki/ASCII

These suggestions also highly depends on environment (e.g. keyboard map).

(An example of local problem is if using Czech/English keyboard switch
("password1234 is not password+ěšč") or with qwerty/qwertz layout
and suggestions like "try to not use y/z in passphrase to avoid the problem".

Another common problem is  "please check that you have NumLock
switched on when entering digits".

Of course, 5 of 4 admins likes late night calls from users crying
"my password doesn't work!"... :-)

That said, there is no limitation in cryptsetup or dmcrypt regarding
input character set.

All these suggestions are quite generic and are intended to prevent
problem with different environments (locales, keyboard layout etc).

(My suggestion is better use longer non-dictionary ascii-friendly passphrase
than using non-ascii characters in it. But if you disagree, just ignore this
suggestion - it will work.... until you need to unlock external drive
on system with foreign keyboard and locales... :-)

Milan

  reply	other threads:[~2011-07-08 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 21:11 [dm-crypt] Note: Characters inadvisable in Passphrases Arno Wagner
2011-07-08 22:05 ` Milan Broz [this message]
2011-07-08 22:34   ` 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=4E177F17.5060303@redhat.com \
    --to=mbroz@redhat.com \
    --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.