From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup won't accept password after normal reboot
Date: Thu, 4 Feb 2010 08:35:59 +0100 [thread overview]
Message-ID: <20100204073559.GA11481@tansi.org> (raw)
In-Reply-To: <loom.20100204T013645-903@post.gmane.org>
On Thu, Feb 04, 2010 at 12:46:46AM +0000, wucherpfennig wrote:
> It's me again. I don't know whether I have to check all languages or anybody can
> explain what happened?
It looks like you have to check all languages that are possible.
You may narrow it down by looking at what could have happen and
by looking at the characters in your passphrase. For example if
you have, say, 12 characters and 9 of them are the same on most
keymaps, then you could try a direct brute force.
> (Probably a script could solve this time wasting exercise?)
It could, but iot looks like you have to write it yourself.
> Anyway, I don't think it's about keyboard settings.
The other option is that you mistyped on creation. One reason
to allways test the passphrase afterwards before doing anything
with the crypto-container.
> (Well I hope it is such a "little" error and nothing serious) I always use
> the settings german switzerland. I remember, while setting up ubuntu, that
> I checked my layout before I entered my password. So I know, what I
> wrote/write. Is there really no way to check my headers or whatever if
> they are broken?
If this is LUKS, then if it asks you for a passphrase,
they should be fine. If is is plain dm-crypt, then there
are no headers that could be corrupt.
> Or which languages do I have to check else? (I checked
> several usa, uk,german, swiss layouts...)
It all depends on what you did wrong.
> pls some help before I have to run over the whole disk...
I gahther this is a new installation and you would only lose
a few hours of configuration work, correct?
I think in that case, doing it again and this time testing the
password at your earliest oportunity would be the best option.
For an encrypted boot, it may also be highly advisable to thest
whether you can decrypt it witha life-cd or unencrypted recovery
system.
Arno
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
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:[~2010-02-04 7:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 0:46 [dm-crypt] cryptsetup won't accept password after normal reboot wucherpfennig
2010-02-04 7:35 ` Arno Wagner [this message]
2010-02-04 19:19 ` Heinz Diehl
2010-02-05 8:31 ` wucherpfennig
-- strict thread matches above, loose matches on Subject: below --
2010-02-04 10:21 wucherpfennig
2010-02-04 13:49 ` Arno Wagner
2010-02-05 8:24 ` wucherpfennig
2010-02-05 14:48 ` Ma Begaj
2010-02-09 7:42 ` wucherpfennig
2010-02-05 8:28 ` wucherpfennig
2010-02-05 10:04 ` wucherpfennig
2010-02-05 17:58 ` Arno Wagner
2010-02-09 7:45 ` wucherpfennig
2010-02-03 20:13 wucherpfennig
2010-02-03 15:32 wucherpfennig
2010-02-03 19:10 ` Heinz Diehl
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=20100204073559.GA11481@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