Jim, please note that the fix in this bug, to get a "clickable" unencryption, only applies to newly created private directories.
Also, this feature isn't really pointless IMHO, it works very well for people without autlogin. With this fix it works reasonably well for autologins as well, it's just quite impossible to transition an already existing private directory to this fix. -- 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 Released Status in “ecryptfs-utils” source package in Ubuntu: Fix Released 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
