[pkg-cryptsetup-devel] Bug#662768: [cryptsetup] New cryptsetup version chokes on old LUKS header

Milan Broz mbroz at redhat.com
Wed Mar 7 13:20:24 UTC 2012


On 03/06/2012 12:19 PM, Milan Broz wrote:

>> LUKS keyslot 4 is invalid.
>> LUKS keyslot 5 is invalid.

So, as expected, there was partition table signature written
over LUKS header.

I added some code to fix it upstream, not enabled by default.
http://code.google.com/p/cryptsetup/source/detail?r=fff8b02b46cc85f22d1b938febdb2df924417cbf

For that particular header it produced:

LUKS keyslot 4 is invalid.
LUKS keyslot 5 is invalid.
Repairing keyslots.
Keyslot 4: offset repaired (318247672 -> 1032).
Keyslot 4: stripes repaired (0 -> 4000).
Keyslot 4: salt wiped.
Keyslot 5: offset repaired (0 -> 1288).
Keyslot 5: stripes repaired (0 -> 4000).
Keyslot 5: salt wiped.
Keyslot 6: bogus partition signature.
Keyslot 6: salt wiped.

(I think you can close this bug now :-)

Milan





More information about the pkg-cryptsetup-devel mailing list