ecryptfs team mailing list archive

[Rune Evjen <rune.evjen@xxxxxxxxx>]

Dustin,

Attached are the pam.d files.

'dpkg -l | grep ecryptfs':
ii  ecryptfs-utils                             53-1ubuntu10                              ecryptfs cryptographic filesystem (utilities
ii  libecryptfs0                               53-1ubuntu10                              ecryptfs cryptographic filesystem (library)

' dpkg -l | grep pam'
ii  bogofilter                                 1.1.7-1ubuntu1                            a fast Bayesian spam filter (dummy package)
ii  bogofilter-bdb                          1.1.7-1ubuntu1                            a fast Bayesian spam filter (Berkeley DB)
ii  bogofilter-common                  1.1.7-1ubuntu1                            a fast Bayesian spam filter (common files)
ii  libpam-ck-connector               0.2.10-1ubuntu8                           ConsoleKit PAM module
ii  libpam-gnome-keyring            2.24.1-0ubuntu1                           PAM module to unlock the GNOME keyring upon 
ii  libpam-modules                      1.0.1-4ubuntu5                            Pluggable Authentication Modules for PAM
ii  libpam-runtime                        1.0.1-4ubuntu5                            Runtime support for the PAM library
ii  libpam0g                                 1.0.1-4ubuntu5                            Pluggable Authentication Modules library
ii  python-pam                            0.4.2-12ubuntu2                           A Python interface to the PAM library


** Attachment added: "common-auth"
   http://launchpadlibrarian.net/18812503/common-auth

-- 
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