Hi,
Am Friday 20 February 2009 11:50:48 schrieb Wearenotalone:
Yesterday i continued looking for a solution to my problem. At first i
changed my volume definition to
volume fskeycipher=aes-256-cbc fskeyhash=sha512
options=fsk_cipher=aes-256-cbc,fsk_hash=sha512,keyfile=/my/encrypted.key,f
Hello,
Bastian Kleineidam schrieb:
Hi,
Am Friday 20 February 2009 11:50:48 schrieb Wearenotalone:
Yesterday i continued looking for a solution to my problem. At first i
changed my volume definition to
volume fskeycipher=aes-256-cbc fskeyhash=sha512
Am Tuesday 24 February 2009 18:45:30 schrieb Wearenotalone:
Anymore questions?
Not at the moment. Your information should be enough to reproduce the problem,
which I will try to do in the next days.
Thanks,
Bastian
signature.asc
Description: This is a digitally signed message part.
Yesterday i continued looking for a solution to my problem. At first i
changed my volume definition to
volume fskeycipher=aes-256-cbc fskeyhash=sha512
I think i have identified the cause of my unmount problem. The mount
option keybits implies the loop option. This causes the LUKS partition
again to be mounted as a loop device. At the moment mount.crypt only
filters the loop option but not the keybits option.
Usualy this is no problem
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
Package: libpam-mount
Version: 1.9-1
Severity: important
After upgrading libpam-mount from the latest Debian Lenny version
(0.44-1+lenny3) to the latest Squeeze version (1.9-1) i get a segfault from
umount.crypt everytime i logout. The encrypted directory is successfully
unmounted, but i get
7 matches
Mail list logo
