[..]
but a function like this or any other
mechanism of header-protection would be nice to see as standard for LUKS.
Especially because the first keyslot is so likely to be corrupted by partition
managers (should be aroud the offset of keyslot 0 where they start to dump their
data?).
has there been any study to find out which ones of the keyslots is most likely to get corrupted accidentally by various tools?
will adding keys from the last slot going backwards add some protection from keys being inaccessible due to accidental header corruption by various tools?
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
