Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0lVGWxsjoOH for ; Wed, 2 Nov 2011 08:23:43 +0100 (CET) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Wed, 2 Nov 2011 08:23:41 +0100 (CET) Message-ID: <4EB0EFF5.2060808@redhat.com> Date: Wed, 02 Nov 2011 08:23:33 +0100 From: Milan Broz MIME-Version: 1.0 References: <20111102031430.GA15717@dentifrice> In-Reply-To: <20111102031430.GA15717@dentifrice> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] password recovery for a luksOpened device? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: mike dentifrice Cc: dm-crypt@saout.de On 11/02/2011 04:14 AM, mike dentifrice wrote: > Or do I necessarily have to jump towards the "How do I recover the > master key from a mapped LUKS container?" FAQ entry? You can run that script mentioned there (it will generate master-key-file from active mapping). And then (instead of format) just run cryptsetup luksAddKey --master-key-file= and add new arbitrary passphrase. (If cryptsetup there doesn't support this option, you can do it on LUKS header clone outside of server and copy it back with new keyslot.) Without using dictionary or brute force attack you cannot recover original passphrase though. In any case, save "dmsetup table --showkeys" output, it will allow to map device even if you destroy LUKS header. Milan