Vincent Fourmond wrote: > > The changelog of cryptsetup says: > > - new libcryptsetup API (documented in libcryptsetup.h) > > > > So it should not be too hard to adapt pmount to the new API. > > Except that pmount does not use libcryptsetup, but only the cryptsetup > binary... So that does not explain everything ;-)...
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. Regards, Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
