Hey, On 06/01/2009 mum laris wrote: > 2) sudo cryptsetup create sda10 /dev/sda10 > --key-file=/mnt/"long_path_to_my"/sda10 > Command failed: Key processing error: Could not read 32 bytes from key > file > > So, may be system expect a 32bit key, also if I've use a shortest one > and this is the reason for which auto-mount fails during startup? Is > there a way to explain it that: ok the key is shortest of what do You > expect, but... please don't say it anymore? The issue here is that plain dm-crypt mapping requires a keyfile with at least 32 bytes. iirc this is not the case for LUKS mappings, but I'm not sure about that. If I got you right, then you used a passphrase to originally create the dm-crypt mapping, and now you tried to setup mapping for the same device with a keyfile containing the passphrase instead of using the passphrase input prompt. Even if this works in theory (i'm still not sure about it), then the requirement of a key larger or equal to 32 bytes still applies. So you'll have to use a passphrase with more than 32 bytes. And no, there's no way to make cryptsetup ignore this requirement. Why don't you use the --key-file facility with a real random key in the first place to setup your dm-crypt mapping? greetings, jonas --------------------------------------------------------------------- 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
