At Thu, 15 Mar 2007 07:14:45 +0100, Henrik Holst <henrik.holst@xxxxxxxxxx> wrote: > > On Tue, 2007-03-13 at 02:01 -0700, Sam's Lists wrote: > [snip] > > Here's the output of cryptsetup luksDump /dev/loop0 (I've gone ahead and > > snipped some of it. Let me know if you really need it all. Can't really > > see why I should share my salt unless it's useful. :) > > If we could use anything with the salt value in the non-encrypted part > of the luks header, then luks would be terrible insecure! > > I did not stay around with luks long enough to think about things like > this. Instead I stay up late worrying about "legacy" mode disappearing > from cryptsetup in newer versions. :-) We already coordinated cryptsetup-luks to take over official cryptsetup and I planned this to happen with the release of 1.0.5, which I'm unfortunately not able to do ATM as I'm busy with preparing two talks that are quite important to me. (The 1.0.5 should be out at mid-April when my work queue resumes normal levels). However, as the new designated maintainer of cryptsetup I promise that the regular cryptsetup mode won't disappear. You don't need to call it legacy. -- Fruhwirth Clemens - http://clemens.endorphin.org --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
