Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kde environment, unlocking gnome keyring fails #1193

Open
promeneur opened this issue Aug 28, 2019 · 1 comment
Open

kde environment, unlocking gnome keyring fails #1193

promeneur opened this issue Aug 28, 2019 · 1 comment

Comments

@promeneur
Copy link

openSuse Leap 15.1
kde environment (sddm)
Skype app uses gnome keyring also in kde environment.
If you install skype package then this installs all about gnome keyring technology.

Login password is the same as gnome keyring password.

During kde session login skype is launched automatically then gnome keyring asks for user the password to open gnome keyring according to get id and pwd for skype connecting.

We can conclude that login process does not unlock gnome keyring (kwallet unlocking succeeds). This is the problem. i want to unlock the 2 storages during logging process.

I check that statements about gnome keyring are well added to

common-auth-pc

auth required pam_env.so
auth optional pam_gnome_keyring.so
auth optional pam_kwallet5.so
auth required pam_unix.so try_first_pass

common-passsword-pc

password requisite pam_cracklib.so
password optional pam_gnome_keyring.so use_authtok
password optional pam_kwallet5.so
password required pam_unix.so use_authtok nullok shadow try_first_pass

common-session-pc

session optional pam_systemd.so
session required pam_limits.so
session required pam_unix.so try_first_pass
session optional pam_umask.so
session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm
session optional pam_kwallet5.so
session optional pam_env.so

With seahorse we can check there are 2 keyrings:

  • "login" which contains Skype id and pwd
  • "Connexion" which contains "login password"

For "login" we can check that "default" is in grey
For "Connexion" we can check that "default" is not in grey

If I use lightdm to open a kde session then unlocking gnome keyring succeeds.

In /var/log/messages i get this error message:

2019-08-27T20:04:08.866459+02:00 grognon su: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
2019-08-27T20:04:08.866678+02:00 grognon su: gkr-pam: couldn't unlock the login keyring.

@promeneur promeneur changed the title kde environment kde environment, unlocking gnome keyring fails Aug 28, 2019
@davidosomething
Copy link

davidosomething commented Dec 15, 2019

2nd, using manjaro kde
SDDM v 0.18.1-1

#%PAM-1.0

auth		include		system-login
auth            optional        pam_gnome_keyring.so
auth		optional	pam_kwallet5.so
account		include		system-login
password optional pam_gnome_keyring.so use_authtok
password	include		system-login
session		include		system-login
session		optional	pam_gnome_keyring.so auto_start
session		optional	pam_kwallet5.so auto_start

login, kwallet, and gnome keyring share the same password for the Login keychain

see also #1058 and https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28
and https://gitlab.gnome.org/GNOME/gnome-keyring/issues/37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants