ecryptfs team mailing list archive
-
ecryptfs team
-
Mailing list archive
-
Message #00180
[Bug 259631] Re: Cannot open Private directory after a reboot
$ keyctl show
Session Keyring
-3 --alswrv 1000 -1 keyring: _uid_ses.1000
404603209 --alswrv 1000 -1 \_ keyring: _uid.1000
$ cat ~/.ecryptfs/Private.sig
[removed]
Not the same... I recall doing this before and they did match (see
earlier in this thread).
--
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
Follow ups