ecryptfs team mailing list archive
-
ecryptfs team
-
Mailing list archive
-
Message #00073
[Bug 259631] Re: Cannot open Private directory after a reboot
I have been running Intrepid since alpha3, and installed it using the
command line instructions in the release notes. I did however already
have ecryptfs as I already used it in a more manual way. (adding the
passphrase=login password using ecyprfs-manager).
When running 'ecryptfs-unwrap-passphrase' I the message
"Unable to read salt value from user's .ecryptfsrc file; using default fa0ec2dfef0ab60d305d97d36a5c...."
and the fa0... part is the actual response, which is not my password.
'echo $?' gives "0"
I have no funny characters in my login phrase and quoting it does not
make a difference to the output.
Regards,
Rune
--
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: Invalid
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:
jimk@intrepid:~$ mount.ecryptfs_private
keyctl_search: Required key not available
When I go to create a key, I get the following message:
jimk@intrepid:~$ 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