From: Milan Broz <mbroz@redhat.com>
To: Rookcifer <rookcifer@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Major Problem with luksAddKey
Date: Wed, 09 Mar 2011 11:27:05 +0100 [thread overview]
Message-ID: <4D7755F9.2070709@redhat.com> (raw)
In-Reply-To: <4D76E1FE.8030509@gmail.com>
On 03/09/2011 03:12 AM, Rookcifer wrote:
> I am using LUKS/dm-crypt to encrypt a storage drive I have (sdb). I
> wanted to change the LUKS passphrase on this volume, so I ran the
> following command:
>
> cryptsetup luksAddKey /dev/sdb1
>
> I was prompted for my passphrase and slot 0 was unlocked. Then I went
> to enter the new passphrases, so I entered it and was asked to verify.
> I entered it again. It gave me a prompt that the passwords did not
> match. No big deal, right? I must have mistyped. So I went through
> the process again, but this time I was not able to unlock the master
> key! I am now locked out of my volume completely and I have no idea
> what to do.
>
> Is this a bug or did I do something wrong? I should not be locked out
> of my volume after failing to change the pass phrase!
Of course it should work. But you have not specified important info:
cryptsetup version? cryptsetup with the --debug output? which distro?
some erors in syslog? (io errors?)
if it is broken now, also luksDump of the partition.
cryptsetup should never touch original keyslot area, so even if
adding new fails, the old must always stay the same.
Milan
next prev parent reply other threads:[~2011-03-09 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 2:12 [dm-crypt] Major Problem with luksAddKey Rookcifer
2011-03-09 10:27 ` Milan Broz [this message]
2011-03-09 10:32 ` Jonas Meurer
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=4D7755F9.2070709@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=rookcifer@gmail.com \
/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.