From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <spamzad@googlemail.com>
Received: from mail-fx0-f217.google.com (mail-fx0-f217.google.com
	[209.85.220.217]) by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Tue, 25 Aug 2009 01:10:57 +0200 (CEST)
Received: by fxm17 with SMTP id 17so1889708fxm.13
	for <dm-crypt@saout.de>; Mon, 24 Aug 2009 16:10:57 -0700 (PDT)
Date: Tue, 25 Aug 2009 01:10:54 +0200
From: Martin <spamzad@googlemail.com>
Message-ID: <20090825011054.702a5766@Computername>
In-Reply-To: <h6v5ff$e08$1@ger.gmane.org>
References: <20090824100211.5c162f1a@Computername>
	<4A92B7F9.7060102@redhat.com> <h6v5ff$e08$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [dm-crypt] Broken header of a luks-partition - more than once
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 Tue, 25 Aug 2009 00:50:23 +0200
Thomas B=C3=A4chler <thomas@archlinux.org> wrote:


> Milan Broz schrieb:
> > But see crypttab here - you have tmp device created as regular
> > encrypted device with random key - are you sure that kernel
> > _cannot_ swap sda & sdb and your system just formats temp device
> > here?
> >=20
> >> # <target name> <source device>         <key file>      <options>
> >> home            /dev/sdb2               none            luks
> >> ctmp            /dev/sda2               /dev/urandom
> >> tmp,cipher=3Daes-cbc-essiv:sha256
> >> cswap           /dev/sda5               /dev/urandom
> >> swap,cipher=3Daes-cbc-essiv:sha256
>=20
> Milan is probably right here, device names on modern distributions
> are not deterministic! However, the underlying script should be
> careful not to the device under the random key mapping if it contains
> a valid filesystem.
>=20
> crypttab functionality is not part of cryptsetup, but part of your=20
> distribution. You should report this problem there.
>=20
Okay, I assume that is a quite good point - i didn't know this fact.. I
thought crypttab is part of cryptsetup and has - more or less - nothing
to do with anything else in first place.
Since the failure takes some time to happen, I will probably report back
in a couple of days or weeks. Thanks a lot for your time :)
Would really not have thought of that!


Martin