From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
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 mijliIS4a4_f for <dm-crypt@saout.de>;
 Mon,  2 Apr 2012 13:15:52 +0200 (CEST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Mon,  2 Apr 2012 13:15:52 +0200 (CEST)
Message-ID: <4F798A64.4000009@redhat.com>
Date: Mon, 02 Apr 2012 13:15:48 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <CAFnMBaSPn6p_jLcgJOQ_D=STpJrwRap6qorCcenH7ez+bGmPiQ@mail.gmail.com>
 <CAFnMBaR24NYrMLh2M+jskXfUSAJSsmwh3CvA=aR_Tkpkd6Sw=w@mail.gmail.com>
 <4F79665F.8080706@redhat.com>
 <CAFnMBaS63WvxydnvMmhfXBjLKh4KkxYGg_CABHM3ypP6_63Zog@mail.gmail.com>
 <CAFnMBaSZCj+cxdpZQ8URBA3VqwOF8tMh8PVkOg4dPeP_St+O8Q@mail.gmail.com>
In-Reply-To: <CAFnMBaSZCj+cxdpZQ8URBA3VqwOF8tMh8PVkOg4dPeP_St+O8Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] about invalid key slots
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt@saout.de

On 04/02/2012 12:10 PM, .. ink .. wrote:
> on-disk-format.pdf says key-slot-2 is at offset 256, luksDump says its at 264. Is this expected?

Seems I sent that just private - so here: 256 is offset in bytes of keyslot info struct
in LUKS header, 264 is value (stored in this info struct) describing offset of keyslot area
on disk, in sectors.

IOW two separate things.

Milan