From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iy0-f178.google.com (mail-iy0-f178.google.com [209.85.210.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Wed, 9 Mar 2011 03:12:18 +0100 (CET) Received: by iyj8 with SMTP id 8so89706iyj.37 for ; Tue, 08 Mar 2011 18:12:17 -0800 (PST) Message-ID: <4D76E1FE.8030509@gmail.com> Date: Tue, 08 Mar 2011 20:12:14 -0600 From: Rookcifer MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [dm-crypt] Major Problem with luksAddKey List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de 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