I did set the suid bit on /sbin/mount.ecryptfs_private
After that, "ecryptfs-mount-private" is still broken. It has the appearance of working. The Private directory is mounted. But in the mounted ~/Private only the encrypted file names show.
If "modprobe ecryptfs" is run before "ecryptfs-mount-private" then it works fine.
It seems that "ecryptfs-mount-private" is loading the module, but is loading it too late for it to be usable for decrypting the file names.
After "ecryptfs-mount-private" you can run "ecryptfs-umount-private" followed by another "ecryptfs-mount-private" to get it mounted properly. Or you can tell the system to always load the ecryptfs module.
I think this is related.
I did set the suid bit on /sbin/mount. ecryptfs_ private
After that, "ecryptfs- mount-private" is still broken. It has the appearance of working. The Private directory is mounted. But in the mounted ~/Private only the encrypted file names show.
If "modprobe ecryptfs" is run before "ecryptfs- mount-private" then it works fine.
It seems that "ecryptfs- mount-private" is loading the module, but is loading it too late for it to be usable for decrypting the file names.
After "ecryptfs- mount-private" you can run "ecryptfs- umount- private" followed by another "ecryptfs- mount-private" to get it mounted properly. Or you can tell the system to always load the ecryptfs module.
To me, this looks like a bug.