[Pkg-cryptsetup-devel] Bug#460409: Bug#460409: [dm-crypt] Re: [tobi at coldtobi.de: Bug#460409: cryptsetup: Cannot add Key to LUKS partition]

[Jonas Meurer]

On 23/01/2008 Clemens Fruhwirth wrote:
> At Mon, 21 Jan 2008 19:17:36 +0100,
> Jonas Meurer wrote:
> > 
> > On 21/01/2008 Clemens Fruhwirth wrote:
> > > Jonas Meurer wrote:
> > > 
> > > My main intention was to prevent multiple luksOpen'd devices, as this
> > > (in my opinion) is usually not neccessary and most likely an
> > > error. But using luksAddKey on an opened partition seems reasonable.
> > 
> > so do you plan to fix this in future releases?
> 
> Yes. What about "luksFormat/luksOpen requires exclusive access,
> everything else doesn't"?

sounds like the way to go ... ;)

btw, do you have pending changes which are not in the svn repository yet
(like the patch regarding slots from u.kuehn)? and what about releasing
cryptsetup 1.0.6?

i'd like to upload a new cryptsetup to debian soon. debian lenny will be
released as stable in the second half of 2008, and i'd like to have a
stable cryptsetup package for that as early as possible.

> Btw. we really want exclusive access for luksOpen. As I just tried,
> it's possible to luksOpen a device multiple times, for instance as
> foo1 and foo2, and mount both identical mappings simultaneously. One
> gets nice corruptions when accessing both file system that both
> believe that they have exclusive access to the underlying device but
> in reality share a device.

greetings,
 jonas