All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] valid passphrase not accepted
Date: Wed, 27 Oct 2010 17:56:12 +0200	[thread overview]
Message-ID: <20101027155612.GA23215@tansi.org> (raw)
In-Reply-To: <20101027143923.GA10534@fancy-poultry.org>

I am currently assisting the OP offline. Seems the LUKS
header was overwritten in some fashion.

Arno

On Wed, Oct 27, 2010 at 04:39:23PM +0200, Heinz Diehl wrote:
> On 27.10.2010, ts0@dotlike.net wrote: 
> 
> > after rebooting i wasn?t able to unlock the luks-partition.
> > the luks header is there. the kernel configuration hasn?t changed
> > (all ciphers are integrated). the passphrase is valid but not
> > accepted.
> 
> A shot in the dark: do you use the same keymapping when you're entering
> the passphrase as you did while LUKS-formatting the drive?
> 
> _______________________________________________
> 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 

  reply	other threads:[~2010-10-27 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 12:15 [dm-crypt] valid passphrase not accepted ts0
2010-10-27 14:01 ` Arno Wagner
2010-10-27 14:39 ` Heinz Diehl
2010-10-27 15:56   ` Arno Wagner [this message]
2010-10-27 16:07     ` Rick Moritz
2010-10-27 16:16       ` Arno Wagner
2010-10-27 16:23       ` Heinz Diehl
2010-10-27 18:57         ` 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=20101027155612.GA23215@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.