On Sunday 2009-03-01 19:09, Wearenotalone wrote:
>>
>> For your specific problem, omit the "loop" option in the options=
>> in <volume>.
>>
>> I do not think this has anything to do with the keybits option.
>>
>>
> I never explicitly used the "loop" option[...]
Yes, but mount(8) decided to setup one before calling crypt_LUKS:
>mount.crypt_LUKS(mtcrypt.c:155): loop mount option ignored
Hm. It seems to have been keysize after all (I could reproduce it):
# mount -v x.cont /mnt -o
fsk_cipher=aes-256-cbc,fsk_hash=sha512,keyfile=/my/encrypted.key,fsck,noexec,nodev,nosuid,relatime,cipher=aes-cbc-essiv:sha256,keybits=256,hash=sha512
mount: going to use the loop device /dev/loop0
Without keyfile, mount(8) will not set up the loop device.
But the bug here is actually that you did not specify fstype="crypt"
in pam_mount.conf.xml. One has to explicitly state the fstype
to mount(8) for any pseudo filesystem if it uses options that
conflict with mount itself.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
