FS#9218 - kde-common: upgrade overrides /etc/pam.d/kde*
Attached to Project:
Arch Linux
Opened by Apollon Oikonomopoulos (apoikos) - Tuesday, 15 January 2008, 09:39 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 26 January 2008, 16:14 GMT
Opened by Apollon Oikonomopoulos (apoikos) - Tuesday, 15 January 2008, 09:39 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 26 January 2008, 16:14 GMT
|
Details
Description:
kde-common does not list /etc/pam.d/kde* as configuration files. Thus any upgrade of the package simply overwrites the older pam configuration files, discarding any manual changes made. This behaviour conflicts with the standard used by pacman for configuration files. Additional info: * package version: 3.5.8-2 Steps to reproduce: 1. Make changes to /etc/pam.d/kde or /etc/pam.d/kde-np 2. Upgrade or re-install kde-common 3. The kde* files under /etc/pam.d/ are replaced by those in the package |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Saturday, 26 January 2008, 16:14 GMT
Reason for closing: Fixed
Additional comments about closing: 3.5.8-3
Saturday, 26 January 2008, 16:14 GMT
Reason for closing: Fixed
Additional comments about closing: 3.5.8-3
base/pam
base/coreutils
support/sudo
support/openssh
Of course the user is supposed to modify the pam.d files, that's what they're there for ;-) IMHO the pam.d files should definitely be backed up as they interfere with system authentication (a rather critical function). I use kerberos authentication (pam_krb5.so) at work, and today I couldn't login via KDM because of the kde-common upgrade. Furthermore, imagine if openssh for example did replace the pam.d/ssh file and you ended up locked out of a server - with no physical access - using pam_ldap.so.