[pkg-cryptsetup-devel] Bug#493848: Bug#493848: Still a problem

Jonas Meurer jonas at freesources.org
Fri Aug 8 01:01:35 UTC 2008


On 07/08/2008 Sebastian Moster wrote:
> there still seems to be a problem concerning the key-file parameter when
> read from /etc/crypttab.
> With 2:1.0.6-5, the script produces now the command
> 
> cat keyfile | cryptsetup -c .... -s  --key-file=- create
> 
> which seems to be correct. However, this does somehow not produce the
> same result as if I call manually
> 
> cryptsetup -c ... -s --key-file=keyfile
> 
> So when I call the second version, I can mount the encrypted partitions
> whithout problems. With the first version, and especially when booting,
> they cannot be mounted.

you're right. I was able to reproduce the bug. It seems like 'cryptsetup
create' for plain dm-crypt mappings treats keyfiles different from
luksOpen.

David: the only solution I can imagine for lenny is to revert do_noluks()
to not use cat for keyfiles at all. What do you think about that?

greetings,
 jonas





More information about the pkg-cryptsetup-devel mailing list