ecryptfs team mailing list archive
-
ecryptfs team
-
Mailing list archive
-
Message #00090
[Bug 259631] Re: Cannot open Private directory after a reboot
Yes, I didn't realize that it was asking for my login password;
temporary brain cramp. I can type my password twice though... :)
So, I put in a different password, thinking it was for mounting the
encrypted folder. Then I put it in a 2nd time to confirm. Then it asked
for another password, I put in the same one, at this point, I realized
that I was doing something wrong, but I can't go back, so I put it in a
4th time.
So, I wanted to recreate it properly with the --force command. That
didn't work at first, but now it does. Except for the reboot part. When
I recreate it now, with the --force command, just in case, I put in my
login password twice, then a different passphrase of my choosing. Every
reboot, I get the error above.
--
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:
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