Comment # 32 on bug 1209741 from
> > Since systemd-user and sddm both execute during the login process,
> > systemd-user with that change will create ( using revoke force ) the
> > keyring, but if it is left in /etc/pam.d/sddm then when that is processed
> > after systemd-user since sddm also uses revoke and force then it will
> > replace the keyring that was just created in systemd-user.
> >
> > Surely that cannot be correct ???
> 
> It is. Otherwise only systemd user services get a session keyring, but not
> processes started by the session itself. See comment 4.

I'm curious, are you aware of ANY other services/programs which use this
session keyring besides pam_cifscreds?


You are receiving this mail because: