Vincent Fourmond wrote: > > I grabbed the source and modified it slightly to print cryptsetup's console > > output, which is shown below with pmount's debugging mode enabled: > > > > spawnv(): executing /sbin/cryptsetup '/sbin/cryptsetup' 'isLuks' > > '/dev/sdb1' > > spawn(): /sbin/cryptsetup terminated with status 0 > > spawnv(): executing /sbin/cryptsetup '/sbin/cryptsetup' 'luksOpen' > > '/dev/sdb1' '_dev_sdb1' > > device-mapper: status ioctl failed: Permission denied > > Enter passphrase for /dev/sdb1: > > device-mapper: create ioctl failed: Permission denied > > Failed to setup dm-crypt key mapping for device /dev/sdb1. > > Check that kernel supports aes-cbc-essiv:sha256 cipher (check syslog for > > more info). > > Failed to read from key storage. > > spawn(): /sbin/cryptsetup terminated with status 251 > > > > I really don't get it as cryptsetup is invoked the same way as in prior > > versions, but fails now. > > Sounds like a cryptsetup bug, doesn't it ? Or is it a problem with the > newer version of libselinux ? Do you have a SELinux-active kernel ? > > What does syslog/dmesg say ? And what if you run manually cryptsetup > with the exact same command-line ?
I don't have SELinux active. Neither syslog nor dmesg contain anything about pmount/cryptsetup, and invoking cryptsetup manually with the paramteters from pmount's output (/sbin/cryptsetup luksOpen /dev/sdb1 _dev_sdb1) works without problems. May this be some environment specific problem? Regards, Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
