When dev-libs/libgcrypt is built with USE=caps, sys-fs/cryptsetup will fail in the following way: fd = open("/dev/mapper/control", ...); -EACCES = ioctl(fd, DM_VERSION, ...) Resulting in a message telling you dm_mod isn't loaded or isn't initialized yet. -EACCES is returned from the ioctl() if the calling process doesn't have CAP_SYS_ADMIN. ref: http://lxr.linux.no/#linux+v3.8.10/drivers/md/dm-ioctl.c#L1662 We likely should require libgcrypt to be built without USE=caps
wuahhh, *THIS* stopped my fully encrypted server to boot. :-/ thanks for reporting! I guess, the importance of this bug should be higher!
*** Bug 467798 has been marked as a duplicate of this bug. ***
Is there something to check/test, I just spent an hour trying to figure this out on my workstation :(
Ijust work on this when I tried to set up cryptsetup on my laptop.Steps to reproduce the bug are : * emerge libgcrypt with USE=caps enabled * emerge cryptsetup * (optinally create a loop file device or use a diskpartition) dd if=/dev/null of=/tmp/file bs=1048576 seek=1024 losetup /dev/loop0 /tmp/file * cryptsetup luksFormat /dev/loop0 (or /dev/sd??) * open the secure container cryptsetup open --type luks /dev/loop0 secure The latest command failed. Also see this bug report for additional info http://code.google.com/p/cryptsetup/issues/detail?id=47
This isn't an issue anymore since the caps use flag was removed from libgcrypt.
