Jeff Layton writes:
On Wed, 08 Aug 2012 19:45:33 +0200
Milan Knížek <knizek.confy@xxxxxxxxx> wrote:
> pam_keyinit.so was already in /etc/pam.d/gdm-password, though when
> logged in into Xfce from GDM, then "cifscreds add" typed in
> xfce4-terminal complains about non-persistent keyring.
>
> I can see that the name of the top level keyring differs for Xfce session:
> Session Keyring
> 666176370 --alswrv 1001 -1 keyring: _uid_ses.1001
> 132272983 --alswrv 1001 -1 \_ keyring: _uid.1001
>
> Does anyone know if that is some GDM bug/feature and how avoid it?
>
An excellent question. I see the same behavior on a fairly stock Fedora
17 host too. I can only assume that the actual desktop session is
ending up with a different keyring session than gdm had.
For the sake of curiosity, when logging in remotely with x2go (based on NX),
the session keyring is okay:
$ keyctl show
Session Keyring
420490248 --alswrv 1000 100 keyring: _ses
318990990 --alswrv 1000 -1 \_ keyring: _uid.1000
909936426 --alswrv 1000 100 | \_ user: 75fbf6399a9cf084
909201030 --alswrv 1000 100 | \_ user: aa10afc0620e9893
256104206 ----sw-v 1000 100 \_ logon: cifs:a:192.168.1.3
(That is for another user, the extra keys are for ecryptfs).
Later on I will try to run startx from console as well to see if GDM is the
suspect.
Milan
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
