ecryptfs team mailing list archive
-
ecryptfs team
-
Mailing list archive
-
Message #00258
[Bug 259631] Re: Cannot open Private directory after a reboot when "Automatic Login" enabled
Judging by the comments in #48 above, I suspect my problem is related.
I can log in to my test machine at the keyboard, and the ~/Private
directory is properly mounted. SSH in using public keys
(authorized_keys), and it is not mounted.
ccurley@grissom:~$ /sbin/mount.ecryptfs_private
keyctl_search: Required key not available
ccurley@grissom:~$ keyctl show
Session Keyring
-3 --alswrv 1000 -1 keyring: _uid_ses.1000
202034337 --alswrv 1000 -1 \_ keyring: _uid.1000
ccurley@grissom:~$
I believe that indicates that the keyring is empty.
I ran through Mr. Kirkland's exercise in comment 13 above, and was able
to mount the directory correctly.
ccurley@grissom:~$ ll Private/
total 20
drwx------ 2 ccurley ccurley 4096 2008-11-06 18:57 .
drwxr-xr-x 36 ccurley ccurley 4096 2008-11-06 20:31 ..
-rw-r--r-- 1 ccurley ccurley 15 2008-11-06 18:57 test
ccurley@grissom:~$
I hope the proposed fix handles the case of SSH as well.
--
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 Committed
Status in “ecryptfs-utils” source package in Ubuntu: In Progress
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