http://bugzilla.novell.com/show_bug.cgi?id=499711 Summary: pam-config -a --ssh --ssh-try_first_pass produces broken /etc/pam.d/common-session-pc Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team@suse.de ReportedBy: tilman.vogel@web.de QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.0.10) Gecko/2009042700 SUSE/3.0.10-2.1 Firefox/3.0.10 The produced file prevents logging in. try_first_pass is not even needed in the session line. Reproducible: Always Steps to Reproduce: 1. run "pam-config -a --ssh --ssh-try_first_pass" 2. look at /etc/pam/common-session-pc Actual Results: #%PAM-1.0 # # This file is autogenerated by pam-config. All changes # will be overwritten. # # Session-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define tasks to be performed # at the start and end of sessions of *any* kind (both interactive and # non-interactive # session required pam_limits.so session required pam_unix2.so session optional pam_umask.so session optional pam_ssh.so try_first_pass Expected Results: #%PAM-1.0 # # This file is autogenerated by pam-config. All changes # will be overwritten. # # Session-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define tasks to be performed # at the start and end of sessions of *any* kind (both interactive and # non-interactive # session required pam_limits.so session required pam_unix2.so session optional pam_umask.so session optional pam_ssh.so Trying to fix the file by using pam-config -d --ssh --ssh-try_first_pass fails because pam-config will be confused by its own mistake. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.