ecryptfs team mailing list archive
-
ecryptfs team
-
Mailing list archive
-
Message #00381
[Bug 259631] Re: Cannot open Private directory after a reboot when "Automatic Login" enabled
I still an unable to mount the private directory. When I run 'ecryptfs_insert_wrapped_passphrase_into_keyring ~/.ecryptfs/wrapped-passphrase PASSPHRASE' it tells me the command is not found, changing it to 'ecryptfs-insert-wrapped-passphrase-into-keyring ~/.ecryptfs/wrapped-passphrase PASSPHRASE' gives me Unable to read salt value from user's .ecryptfsrc file; using default
Error attempting to unwrap passphrase and insert into the user session keyring; rc = [1]. Check the system log for more information from libecryptfs.
The log tells me under messages that 'Nov 24 08:55:06 alan ecryptfs-
insert-wrapped-passphrase-into-keyring: Error attempting to parse
.ecryptfsrc file; rc = [-5]' and 'Nov 24 08:55:07 alan ecryptfs-insert-
wrapped-passphrase-into-keyring: Passphrase key already in keyring'
I guess everything is working fine but somehow I am still unable to
mount it. Help is much appreciated.
--
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:
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