I get the same problem. Working with Jaunty amd64, my home directory mounts fine when it is all done automatically, but when I try to do it by hand (as root from the latest Jaunty LiveCD as part of a system diagnostic run), I get the results described in #4 above: Filenames decrypted properly, but "No such file or directory."
Note that mount.ecryptfs reports that it is doing the following: """ Attempting to mount with the following options: ecryptfs_unlink_sigs ecryptfs_fnek_sig=a521ad46fa60c9c7 ecryptfs_key_bytes=16 ecryptfs_cipher=aes ecryptfs_sig=a521ad46fa60c9c7 """ I.e. it is using the *SAME* signature for both fnek and file contents. That should explain the symptoms. The problem seems to be with the user utils. No matter what combination of command line options (mount -o ...) or interactive input I use, the fnek signature always gets used for both ecryptfs_fnek_sig and ecryptfs_sig. Since I can mount my home directory automatically with no problems, it would seem that there a way of decrypting the files without going through the user tools. Is that the case? Can a workaround be built from that? -- "mounting eCryptfs: [-2] No such file or directory" when trying to mount encrypted home https://bugs.launchpad.net/bugs/455709 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
