Bug ID 1114258
Summary Latest update of kcheckpass breaks custom PAM configuration
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component KDE Workspace (Plasma)
Assignee opensuse-kde-bugs@opensuse.org
Reporter bjoernv@arcor.de
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Since the latest kscreenlocker changes to resolve bug #931296 manual changes of
/etc/pam.d/kscreenlocker get lost after each kscreenlocker update.

It is not important, which manual changes are made. I show my changes as an
example. My desktop is secured with a Yubikey as a second factor:

$ cat /etc/pam.d/kscreenlocker
#%PAM-1.0
auth     requisite      pam_yubico.so <some additional parameters>
auth     include        common-auth
account  include        common-account
password include        common-password
session  required       pam_loginuid.so
session  include        common-session

If I update kscreenlocker my manual configuration are reset and I get:

$ cat /etc/pam.d/kscreenlocker
#%PAM-1.0
auth     include        common-auth
account  include        common-account
password include        common-password
session  required       pam_loginuid.so
session  include        common-session

No other PAM service shows this problem.


You are receiving this mail because: