I seem to have the same problem. Here's what I did: 1. I ran ecryptfs-setup-private 2. I put in the wrong password, but it succeeded anyway 3. I tried to rerun ecryptfs-setup-private with the --force switch, it wouldn't work 4. There was a PAM update that I saw go through yesterday? Not sure if it's related 5. The --force started to work and I can get it to work, but once I reboot, I lose access and get "keyctl_search: Required key not available" 6. 'ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase LOGIN_PASSPHRASE' returns "Unable to read salt value from user's .ecryptfsrc file; using default" 7. I typed in my own passphrase during setup, Private.sig and 'keyctl show' do return the same value.
-- Cannot open Private directory after a reboot 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-utils” source package in Ubuntu: Incomplete 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
