On Tue, Mar 12, 2002 at 03:51:01PM -0500, Patterson, Ross wrote: > Andrew Morgan <morgan@transmeta.com> writes: > > Please file a bug report: > > Done. [...] > This case does not work as expected - the user cannot log in: > > # cat /etc/pam.d/login > #%PAM-1.0 > auth required /lib/security/pam_dump_info.so before > #auth optional /lib/security/pam_rc.so 3 0 > auth [success=ok new_authtok_reqd=ok default=ignore] \ > /lib/security/pam_rc.so 3 0 > auth requisite /lib/security/pam_unix.so nullok #set_secrpc > auth required /lib/security/pam_dump_info.so after Auth modules are not supposed to return new_authtok_reqd. And yes, the stack should ignore pam_rc:auth's return of PAM_SEVICE_ERR given the above config. [...] > > > > What gives? Anybody understand this stuff? > > > > Well, I thought I did. > > I thought I did too :-) Clearly there must be a bug in libpam. > Ross Patterson > Computer Associates Cheers, Nico -- -DISCLAIMER: an automatically appended disclaimer may follow. By posting- -to a public e-mail mailing list I hereby grant permission to distribute- -and copy this message.- Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
