Re: [dm-crypt] Broken header of a luks-partition - more than once

[Martin <spamzad@googlemail.com>]

On Tue, 25 Aug 2009 00:50:23 +0200
Thomas Bächler <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?
> > 
> >> # <target name> <source device>         <key file>      <options>
> >> home            /dev/sdb2               none            luks
> >> ctmp            /dev/sda2               /dev/urandom
> >> tmp,cipher=aes-cbc-essiv:sha256
> >> cswap           /dev/sda5               /dev/urandom
> >> swap,cipher=aes-cbc-essiv:sha256
> 
> 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.
> 
> crypttab functionality is not part of cryptsetup, but part of your 
> distribution. You should report this problem there.
> 
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