PAM
I’ll come out and say it - I don’t get PAM… it’s the worst of weirdest of weird incantations and magic potion of a config file that will make or break your config
Switched to GNOME
So I’ve got a frankenlinux desktop now - installed gnome on Kde neon distro that I have running… To be honest, it was more to check what I was missing on wayland. At least gnome provides a workable wayland experience with Nvidia. While I understand KDE’s motivations of not to bend for Nvidia (F! NVIDIA), that’s what I have;
I like Gnome’s usability better and while Wayland works well, I can’t use it as screen sharing doesn’t seem to be functional on Ubuntu 20.04 (neon’s base)
PAM
And that brings me to today’s topic - PAM. Can’t figure it out. In any case, I was being prompted for keyring password after login and the default keyring wasn’t being unlocked.
-
Default keyring has to be named as 'Login'. I had an additional on called 'Default Keyring' from Plasma that was set as default. Changed default keyring to Login - however, actual keys and passwords now sit in 'Default keyring'
-
Had to install
seahorse
for managing keyrings. -
Had to install
libpam-gnome-keyring
-
Added to
/etc/pam.d/sddm
-auth optional pam_gnome_keyring.so -session optional pam_gnome_keyring.so auto_start
Stuff I reverted
-
Sundry changes under
/etc/pam.d/login
,/etc/pam.d/gdm3-password
-
Changed display manager to
gdm3
fromsddm
, but since reverted this change (back onsddm
)
I have little faith that stuff will work if I go back to Plasma. For now, I’m just in a holding pattern till I migrate over to Arch