From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <wagner@tansi.org>
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 EcC1uKyvBkIM for <dm-crypt@saout.de>;
 Tue,  1 Nov 2011 05:45:27 +0100 (CET)
Received: from v4.tansi.org (ns.km33513-03.keymachine.de [87.118.94.3])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Tue,  1 Nov 2011 05:45:27 +0100 (CET)
Received: from gatewagner.dyndns.org (84-74-163-71.dclient.hispeed.ch
 [84.74.163.71]) by v4.tansi.org (Postfix) with ESMTPA id 9B64F204A87
 for <dm-crypt@saout.de>; Tue,  1 Nov 2011 05:45:27 +0100 (CET)
Date: Tue, 1 Nov 2011 05:45:27 +0100
From: Arno Wagner <arno@wagner.name>
Message-ID: <20111101044527.GB26090@tansi.org>
References: <CAP8O3oPX0Mwc+hMRfVKDqwjPpMquH=dDCLpL-Wc2awFM6EscJA@mail.gmail.com>
 <20111030173230.GA31497@tansi.org>
 <CAP8O3oMseYV46HOg1Uu3L7hb3NFZWf-j10cCqyHUki4K-Ns2Sw@mail.gmail.com>
 <4EADCEF5.2070405@freesources.org>
 <CAP8O3oNnSWO2q5-97XkcpxE-FK7nyyTF1YSSWCf+F+crpr2pEw@mail.gmail.com>
 <4EAE1643.9030501@binarysignals.net>
 <20111031071832.GA9071@tansi.org>
 <4EAF1E95.1070203@freesources.org>
 <CAMw1ynTLyR6L2qMo8B=C1a8GQLE85_xBks+ctzoZMQYCyAd3ug@mail.gmail.com>
 <4EAF25AD.9080200@freesources.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4EAF25AD.9080200@freesources.org>
Subject: Re: [dm-crypt] please HELP - can't acces encrypted LVM after linux
 reinstallation.
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: dm-crypt@saout.de

On Mon, Oct 31, 2011 at 11:48:13PM +0100, Jonas Meurer wrote:
[...]
> I don't suggest to hide the backup header. In fact the exact place of
> it should be obvious (either fixed, or better: random but written to
> the first header). 

I don't think random is doable. After all, people may want to put
a filesystem in there. Or not. You cannot just use some of that
space the layer above expects to be at its disposal. There is really
only one place to put a backup: Right after the first header and
keyslot area, everything else breaks proper layering. And that does 
not really help.

Arno
-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier