https://bugzilla.suse.com/show_bug.cgi?id=1209741 https://bugzilla.suse.com/show_bug.cgi?id=1209741#c7 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |fvogt@suse.com Component|KDE Workspace (Plasma) |Basesystem Assignee|opensuse-kde-bugs@opensuse. |systemd-maintainers@suse.de |org | --- Comment #7 from Fabian Vogt <fvogt@suse.com> --- Reassigning to systemd. (In reply to Joe S from comment #6)

I don't know if you caught this from my bug report but this all used to work and sometime roughly 9 months or so ago it was broken.

Most likely that Plasma enabled systemdBoot by default. Previously it did not make use of systemd user services that much.

From your second link it says:

IIRC the usual advice by Lennart is to use the user-wide @u keyring instead of session keyrings. (Programs searching in @s should automatically find credentials added to @u, as pam_keyinit creates the link by default.)

A few years ago I have asked one affected kernel subsystem (cifs) to allow using @u. They had no interest in doing so. I have since then decided to just give up on being able to use cifs -o multiuser. (See also: GitHub issue regarding AFS PAGs.)

It seems to me like, if cifs used @u and pam_keyinit_so and pam_cifscreds all used @u then all of these problems would go away.

pam_keyinit's purpose is specifically to add a session keyring. So that needs to be fixed in any case. Whether cifscreds should use @u, @s or @us is another topic. -- You are receiving this mail because: You are on the CC list for the bug.