The first solution seems to be incomplete. If the keybits option is
given then the loop device (/dev/loop1) on top of the LUKS partition is
not created (correct behavior), BUT the loop device of the
/my/encrypted.img file (/dev/loop0) is not removed after luksClosing
/dev/mapper/_my_encrypted_img! The result of this is that at every login
a new loop device is attached to the /my/encrypted.img but not removed
after logout. Thats not nice. If you dont use the keybits option then
everything is properly unmounted/luksClosed/detached.
While playing around with version 1.18 i also noticed that not specifing
an keyfile option (not fskeypath="", but keyfile option in options=""!)
causes LUKS to drop this message:
pam_mount(mount.c:67): Command failed: No key available with this
passphrase.
But i will investigate this later and probably open another bugreport.
Best Regards,
WANA
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
