Bug 177331

Description of problem:
login omits pam_acct_mgmt & chauth_tok when authentication is skipped.
Authentication may be skipped, for example, during krlogin because Kerberos
already took care of it. The problem with skipping pam_acct_mgmt is that it
allows users to use the system when maybe they should not be allowed, such that
if they have a Kerberos ticket, the other checks do not apply.

If a user had to use password authentication, pam_acct_mgmt may reject the user
for several reasons: not allowed to use the system at this time, not allowed to
use this system, user's account has been disabled, etc. Why should these tests
be skipped just because the user has a ticket?

Same with pam_chauthtok: the user may have a valid ticket, but if their password
has expired, they need to enter a new one right now.

Version-Release number of selected component (if applicable):
util-linux-2.12a-16.EL4.12

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Here is a patch:
***************
*** 634,650 ****
  	    fprintf(stderr,_("\nLogin incorrect\n"));
  	    pam_end(pamh, retcode);
  	    exit(0);
  	}
  
  	retcode = pam_acct_mgmt(pamh, 0);
  
  	if(retcode == PAM_NEW_AUTHTOK_REQD) {
  	    retcode = pam_chauthtok(pamh, PAM_CHANGE_EXPIRED_AUTHTOK);
  	}
  
  	PAM_FAIL_CHECK;
-     }
  
      /*
       * Grab the user information out of the password file for future usage
       * First get the username that we are actually using, though.
--- 634,650 ----
  	    fprintf(stderr,_("\nLogin incorrect\n"));
  	    pam_end(pamh, retcode);1
  	    exit(0);
  	}
+     }
  
      retcode = pam_acct_mgmt(pamh, 0);
  
      if(retcode == PAM_NEW_AUTHTOK_REQD) {
          retcode = pam_chauthtok(pamh, PAM_CHANGE_EXPIRED_AUTHTOK);
      }
  
      PAM_FAIL_CHECK;
  
      /*
       * Grab the user information out of the password file for future usage
       * First get the username that we are actually using, though.