[Bug 371558] New: yast2 corrupting file /etc/pam.d/ common-account-pc locking out users
https://bugzilla.novell.com/show_bug.cgi?id=371558 Summary: yast2 corrupting file /etc/pam.d/common-account-pc locking out users Product: openSUSE 11.0 Version: Alpha 2 Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: casualprogrammer@yahoo.com QAContact: jsrain@novell.com Found By: Beta-Customer Configuring Network Services with yast2 under certain conditions corrupts /etc/pam.d/common-account-pc, removing the entry account sufficient pam_localuser.so locking out all users, including root. Only access possible is through runlevel 1 The first time it happened, I was configuring LDAP, this time SAMBA, NTP and Xinetd. While the first time I could only recover with a clean install of alpha2 from DVD ( after being able to back up all files, so yast logs are still there ), this time I managed to repair the system with the help of some other users. Notebook: Fujitsu Siemens Amilo Si 1520 Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express Monitor: QUANTADISPLAY LCD Monitor 1280x800@60Hz Wireless: Intel PRO/Wireless 3945ABG Network Connection Sound: 82801G (ICH7 Family) High Definition Audio Controller Desktop: gnome2-SuSE-10.3-168 YaST GUI: yast2-qt-2.16.33-2 OS: openSUSE 11.0 (i586) Alpha3 VERSION = 11.0 Kernel: 2.6.25-rc4-git1-2-pae yast2-2.16.35-2 yast2-users-2.16.16-4 yast2-ldap-2.16.0-11 yast2-ldap-server-2.15.5-142 yast2-samba-server-2.16.0-65 yast2-ntp-client-2.16.4-17 yast2-pam-2.16.0-62 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371558
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c1
--- Comment #1 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=371558
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c2
--- Comment #2 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=371558
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=371558
User sh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c3
Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=371558
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c4
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=371558
User mc@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c5
Michael Calmer
Configuring Network Services with yast2 under certain conditions corrupts /etc/pam.d/common-account-pc, removing the entry
account sufficient pam_localuser.so
locking out all users, including root.
Only access possible is through runlevel 1
Please explain a little bit more verbose what happens. Are you logged-in as a user (maybe root) and you configure with yast a service and after you finished yast the system do an automatic logout and you cannot login anymore? Or after the configuration with yast _you_ do a logout and cannot login anymore? If the second is the case, please attach all /etc/pam.d/common-*-pc files to this bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371558
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c6
Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=371558
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c7
--- Comment #7 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=371558
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c8
--- Comment #8 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=371558
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c9
--- Comment #9 from Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=371558
User mc@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c10
Michael Calmer
https://bugzilla.novell.com/show_bug.cgi?id=371558
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c11
Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=371558
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c12
--- Comment #12 from Jiří Suchomel
Jiri: or does samba-client (or samba-server) configure pam_ldap ?
Samba-server does not configure authentication at all. Samba-client uses pam-config to configure winbind and possibly for setting mkhomedir option. If there's an Active Directory setup, than it also configures kerberos ("krb5"). No LDAP. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=371558
User mc@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c13
Michael Calmer
https://bugzilla.novell.com/show_bug.cgi?id=371558
User mc@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=371558#c14
Michael Calmer
participants (1)
-
bugzilla_noreply@novell.com