Martin- The fix, as proposed, will only solve this comprehensively for *newly* created encrypted-private setups, with the patched ecryptfs-setup-private.
I didn't think it appropriate for upgrading the package to go digging in user's unmounted ~/Private directory, creating symlinks to the readme.txt and .desktop file. If this is really, really what we want, we could hook ecryptfs-mount-private with a *hack*, that would check for the existence of these links in an unmounted Private dir, and create them just before mounting. Is that what you'd want? :-Dustin -- Cannot open Private directory after a reboot when "Automatic Login" enabled https://bugs.launchpad.net/bugs/259631 You received this bug notification because you are a member of eCryptfs, which is subscribed to ecryptfs-utils in ubuntu. Status in eCryptfs - Enterprise Cryptographic Filesystem: Fix Committed Status in “ecryptfs-utils” source package in Ubuntu: Fix Committed Status in ecryptfs-utils in Ubuntu Intrepid: Fix Committed Bug description: Binary package hint: ecryptfs-utils I created an encrypted private directory following the instructions here: https://wiki.ubuntu.com/EncryptedPrivateDirectory Everything worked as it should until I rebooted. When I try to mount my private directory I get the following message: [EMAIL PROTECTED]:~$ mount.ecryptfs_private keyctl_search: Required key not available When I go to create a key, I get the following message: [EMAIL PROTECTED]:~$ ecryptfs-setup-private ERROR: wrapped-passphrase file already exists, use --force to overwrite. I can create a new passphrase if I use the force option, but I shouldn't have to do this everytime I reboot _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
