All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rookcifer <rookcifer@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] Major Problem with luksAddKey
Date: Tue, 08 Mar 2011 20:12:14 -0600	[thread overview]
Message-ID: <4D76E1FE.8030509@gmail.com> (raw)

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!

-- 
--Waiting on ECC

             reply	other threads:[~2011-03-09  2:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09  2:12 Rookcifer [this message]
2011-03-09 10:27 ` [dm-crypt] Major Problem with luksAddKey Milan Broz
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=4D76E1FE.8030509@gmail.com \
    --to=rookcifer@gmail.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.