This bug seems to be related to apparent incompatibilities between the latest libcryptsetup and libgcrypt11. Preliminary experiments with libgcrypt20 indicate that the problems with non-privileged access to LUKS partitions can be fixed simply by compiling with libgcrypt20-dev in place of libgcrypt11-dev.
The attached patch describes these changes. After a bit more testing, I hope to have an updated (minor) release available soon. RW Penney
diff --git a/debian/control b/debian/control index 245d9d6..de31c79 100644 --- a/debian/control +++ b/debian/control @@ -4,12 +4,12 @@ Priority: extra Maintainer: RW Penney <rwpen...@users.sourceforge.net> Homepage: http://cryptmount.sourceforge.net Build-Depends: debhelper (>= 9.0.0), dpkg-dev (>=1.16.1), autotools-dev, - libcryptsetup-dev (>= 1.4), libdevmapper-dev, - libgcrypt11-dev (>= 1.1), pkg-config, uuid-dev + libcryptsetup-dev (>= 1.6), libdevmapper-dev, + libgcrypt20-dev (>= 1.1), pkg-config Standards-Version: 3.9.5 Package: cryptmount -Architecture: any +Architecture: linux-any Depends: ${shlibs:Depends}, ${misc:Depends} Recommends: udev Suggests: openssl, dmsetup
