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 libgcrypt1
Hello Dave,
Thanks for your helpful bug report.
It would appear that this issue is related to changes in libcryptsetup
between versions 1.6.4 and 1.6.6 (which has just entered
debian-testing). The issue you've identified may be related to changes
in libcryptsetup connected with allowing non-privil
Package: cryptmount
Version: 5.0-1
Severity: normal
Dear Maintainer,
I've run into a small issue with cryptmount when I attempt to run it as
my normal user. It reports that it "Failed to initialize device for
LUKS keyfile". However if I run "sudo cryptmount" to give it root
privileges then it w
3 matches
Mail list logo
