** Description changed: Binary package hint: ecryptfs-utils My Private directory does not get mounted after I log in, log out, and log in. Using the ecryptfs-utils commands manually gives me the same result: anders@fixed-disk:~$ ls Private/ [some private files] anders@fixed-disk:~$ ecryptfs-umount-private anders@fixed-disk:~$ ecryptfs-mount-private Enter your login passphrase: Inserted auth tok with sig [c2e0b8f13ee13855] into the user session keyring keyctl_search: Required key not available Perhaps try the interactive 'ecryptfs-mount-private' anders@fixed-disk:~$ ls Private/ THIS DIRECTORY HAS BEEN UNMOUNTED TO PROTECT YOUR DATA -- Run mount.ecryptfs_private to mount again ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: ecryptfs-utils 86-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic x86_64 NonfreeKernelModules: openafs nvidia Architecture: amd64 Date: Sat Feb 26 22:06:27 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202) ProcEnviron: - LANGUAGE=en_US:en - PATH=(custom, user) - LANG=en_US.utf8 - SHELL=/bin/bash + LANGUAGE=en_US:en + PATH=(custom, user) + LANG=en_US.utf8 + SHELL=/bin/bash SourcePackage: ecryptfs-utils + + ==================== + SRU + - Impact: Users who have an encrypted private folder, without filename + encryption, may experience encrypted private mount failures on subsequent + logins. The initial user login will result in a successful mount but once the + user logs out, subsequent logins will fail to automount the encrypted private + folder due to a bug in the automatic key loading. + + - How addressed: The encrypted mount helper logic was failing because of an + invalid error condition. This invalid error condition caused a premature + function return before the required file encryption key was inserted into the + kernel keyring. This fix ignores the invalid error condition and allows for the + file encryption key to be properly inserted into the kernel keyring. + + TEST CASE: Create a test user, "foo". Login under the "foo" user and run + "ecryptfs-setup-private -n" to configure an encrypted private directory without + filename encryption support. Logout and then log back in with the "foo" user + and the encrypted private directory should be properly mounted. Logout and then + log back in with the "foo" user, once again, and the encrypted private + directory will not be mounted. + + - Regression potential: Regression potential is small since the logic modified + in the patch is pretty clean. + + - Minimal patch: The minimal patch is upstream ecryptfs commit r561: + http://bazaar.launchpad.net/~ecryptfs/ecryptfs/trunk/revision/561 + ====================
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/725862 Title: Can’t ecryptfs-mount-private after ecryptfs-umount-private To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/725862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
