← Back to team overview

ecryptfs team mailing list archive

[Bug 460476] Re: ecryptfs: disabling auto-mount diables gdm login

 

I collected some log messages from another failed gdm login like described earlier.
To recap: this is an attempt to login, after ~/.ecryptfs/auto-mount has been removed
to disable the ecryptfs auto-mounting.

I have combined messages from three logs into a chronological order:

daemon.log: Oct 26 00:18:01 bjd-desktop gdm[4298]: pam_sm_authenticate: Called
daemon.log: Oct 26 00:18:01 bjd-desktop gdm[4298]: pam_sm_authenticate: username = [bjd]
daemon.log: Oct 26 00:18:01 bjd-desktop gdm[4298]: Warning: Using default salt value (undefined in ~/.ecryptfsrc)
daemon.log: Oct 26 00:18:03 bjd-desktop gdm[6029]: Skipping automatic eCryptfs mount
auth.log:   Oct 26 00:18:03 bjd-desktop gdm[4298]: pam_unix(gdm:session): session opened for user bjd by (uid=0)
auth.log:   Oct 26 00:18:03 bjd-desktop gdm[6029]: pam_ck_connector(gdm:session): nox11 mode, ignoring PAM_TTY :0
daemon.log: Oct 26 00:18:24 bjd-desktop acpid: client 6009[0:0] has disconnected
daemon.log: Oct 26 00:18:24 bjd-desktop acpid: client connected from 6039[0:0]
syslog:     Oct 26 00:18:24 bjd-desktop acpid: client connected from 6039[0:0]
syslog:     Oct 26 00:18:24 bjd-desktop kernel: [ 1819.829184] agpgart-intel 0000:00:00.0: AGP 3.0 bridge
syslog:     Oct 26 00:18:24 bjd-desktop kernel: [ 1819.829206] agpgart-intel 0000:00:00.0: putting AGP V3 device into 8x mode
syslog:     Oct 26 00:18:24 bjd-desktop kernel: [ 1819.829249] nvidia 0000:01:00.0: putting AGP V3 device into 8x mode
daemon.log: Oct 26 00:18:58 bjd-desktop acpid: client 6039[0:0] has disconnected
daemon.log: Oct 26 00:18:58 bjd-desktop acpid: client connected from 6039[0:0]

The acpid messages I don't know what to make of.  I have an NVidia graphics card, and these acpid
messages occur when I am using the proprietary 'nvidia' driver, and when I'm using the Xorg 'nv' driver,
no change there.

bjd

-- 
ecryptfs: disabling auto-mount diables gdm login
https://bugs.launchpad.net/bugs/460476
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” package in Ubuntu: New

Bug description:
Binary package hint: ecryptfs-utils

ubuntu: Jaunty Jackalope 9.04
uname: Linux bjd-desktop 2.6.28-16-generic #55-Ubuntu SMP Tue Oct 20 19:48:24 UTC 2009 i686 GNU/Linux
source package: ecryptfs-utils_73-0ubuntu6.1_i386.deb (installed the common way through apt)

Is the ecryptfs 'disable auto-mount' feature supposed to work with this version (73)?
Judging from the manual and binaries' options it should.

Here's the bottom line:
Succesfully created an ecryptfs directory, with the command 'ecryptfs-setup-private --noautomount'.
Running this command, among others, one of the reported messages is
'INFO: /home/bjd/Private will not be mounted on login'.
Log out. Try to log in again.
In the gdm box, enter name, enter password. Now after hitting RETURN after entering the password,
gdm seems to hang for ~25s. Login does not succeed. Instead gdm seems to die after those ~25s,
and to immediately restart, presenting me again with the login box.

To remedy this situation, login at a VT, touch ~/.ecryptfs/auto-mount, return to the gdm login screen,
and succesfully login. Of course, at this time the ecryptfs is mounted, but the conclusion is: disabling
auto-mount apparently doesn't seem to allow me to login for some reason.

Additonal information:
- All ecryptfs directories and supporting setup seem to be in place correctly, I have ~/Private, ~/.Private,
~/.ecryptfs, and their content files, and the PAM configuration files all look good: in /etc/pam.d, the files
common-auth, common-password and common-session have their respective ecryptfs modifications:
common-auth:        auth           optional pam_ecryptfs.so unwrap
common-password: password   optional pam_ecryptfs.so 
common-session:    session     optional pam_ecryptfs.so unwrap

- Again retrying several times, manually unmounting ~/Private, removing ~/.ecryptfs/auto-mount and
then login, failed in the same way as described above.

Glad to provide any additional info.

bjd



References