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 y_Dd8WshXtOw for ; Mon, 27 Aug 2012 12:20:42 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Mon, 27 Aug 2012 12:20:41 +0200 (CEST) Message-ID: <503B49EC.8050103@redhat.com> Date: Mon, 27 Aug 2012 12:20:28 +0200 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] solved: Re: How to recover partially overwritten LUKS volume? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: korn-gmail@chardonnay.math.bme.hu Cc: dm-crypt@saout.de, =?ISO-8859-1?Q?Andr=E1s_Korn?= On 08/27/2012 11:51 AM, Andr=E1s Korn wrote: > That means that the offsets from the FAQ don't apply to my LUKS > container and that keyslot #2 has been wiped after all. Not sure if it is good idea to have these in FAQ, it depends on key size. (But there are usually only 3 variants for 128,256 and 512bits). I wonder adding this directly to luksDump would help? Like ... Key material offset: 8 Key slot area offset: 0x1000 - 0x21000 ... (here with padding, perhaps it is better print used area only without paddi= ng...) Milan p.s. very nice description of successful recovery, congrats :)