Please, take a look at bug #268316 first. I can reproduce the setuid problem in =sys-fs/ecryptfs-utils-76 and =sys-fs/ecryptfs-utils-79 that now are available on portage. The symlinks seems to correct though. Reproducible: Always Steps to Reproduce: 1. ecryptfs-setup-private Actual Results: $ ecryptfs-setup-private Enter your login passphrase: Enter your mount passphrase [leave blank to generate one]: ************************************************************************ YOU SHOULD RECORD YOUR MOUNT PASSPHRASE AND STORE IT IN A SAFE LOCATION. ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase THIS WILL BE REQUIRED IF YOU NEED TO RECOVER YOUR DATA AT A LATER TIME. ************************************************************************ Done configuring. Testing mount/write/umount/read... mount: Operation not permitted ERROR: Could Expected Results: mount the encrypted private directory. The suid bit should be set on /sbin/mount.ecryptfs_private instead of /sbin/mount.ecryptfs
This bug should be fixed in sys-fs/ecryptfs-utils-82.
It should? Reopen please: $ emerge -s ecryptfs-utils Searching... [ Results for search key : ecryptfs-utils ] [ Applications found : 1 ] * sys-fs/ecryptfs-utils Latest version available: 82 Latest version installed: 82 Size of files: 501 kB Homepage: http://launchpad.net/ecryptfs Description: eCryptfs userspace utilities License: GPL-2 $ ecryptfs-mount-private Enter your login passphrase: mount: Operation not permitted $ sudo chmod +s /usr/bin/ecryptfs-mount-private $ ecryptfs-mount-private $
Sorry, the chmod command (as root) was: chmod +s /sbin/mount.ecryptfs_private
(In reply to comment #2 and comment #3) Enable "suid" USE flag.
Oh, lol. Sorry, I must be blind ;) But I think that should be the normal state (not a USE flag or a USE flag called "nosuid" or something like that.
