From mboxrd@z Thu Jan 1 00:00:00 1970 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 MgI0TSbKD0V7 for ; Sun, 26 Aug 2012 16:42:50 +0200 (CEST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mail.saout.de (Postfix) with ESMTP for ; Sun, 26 Aug 2012 16:42:50 +0200 (CEST) Date: Sun, 26 Aug 2012 16:42:49 +0200 From: Heinz Diehl Message-ID: <20120826144249.GA2626@fancy-poultry.org> References: <20120825112041.GA28890@tansi.org> <20120825202133.GA7590@tansi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] How to recover partially overwritten LUKS volume? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 26.08.2012, Andr=E1s Korn wrote:=20 > Could it be that cryptsetup tries to use keyslot #1 based on the > passphrase I enter, realizes that it's corrupt and throws an error > without ever trying keyslot #2? But apparently no, because specifying > an explicit --key-slot also fails. AS far as I know, the passphrase is probed against all keyslots, and the one which matches is taken.