Bug#317241: openssh-server: unable to login after upgrade to 4.1p1-5

[Andrew Schulman <andrex@alumni.utexas.net>]

I have the same problem here.  With 4.1p1-4, all users can 
log in as usual via ssh.  With 4.1p1-5, no users can log in.  
With 'LogLevel DEBUG3' set in sshd_config, /var/log/auth.log 
ends with

Jul  6 18:58:39 helium sshd[28455]: debug1: matching key found: file /etc/ssh/portfwd/.ssh/authorized_keys, line 1
Jul  6 18:58:39 helium sshd[28455]: Found matching DSA key: 2f:de:4f:38:08:5e:fe:84:51:2c:76:95:28:43:e4:2b
Jul  6 18:58:39 helium sshd[28455]: debug1: restore_uid: 0/0
Jul  6 18:58:39 helium sshd[28455]: debug3: mm_answer_keyallowed: key 0x80a1f00 is allowed
Jul  6 18:58:39 helium sshd[28455]: debug3: mm_request_send entering: type 21
Jul  6 18:58:39 helium sshd[28455]: debug3: mm_request_receive entering
Jul  6 18:58:39 helium sshd[28455]: debug3: monitor_read: checking request 22
Jul  6 18:58:39 helium sshd[28455]: debug1: ssh_dss_verify: signature correct
Jul  6 18:58:39 helium sshd[28455]: debug3: mm_answer_keyverify: key 0x80a2020 signature verified
Jul  6 18:58:39 helium sshd[28455]: debug3: mm_request_send entering: type 23
Jul  6 18:58:39 helium sshd[28455]: debug3: mm_request_receive_expect entering: type 46
Jul  6 18:58:39 helium sshd[28455]: debug3: mm_request_receive entering
Jul  6 18:58:39 helium sshd[28455]: debug1: do_pam_account: called
Jul  6 18:58:39 helium PAM-warn[28455]: function=[pam_sm_acct_mgmt] service=[sshd] terminal=[ssh] user=[portfwd] ruser=[<unknown>] rhost=[161.80.249.101]
Jul  6 18:58:39 helium sshd[28455]: debug3: PAM: do_pam_account pam_acct_mgmt = 13 (User account has expired)
Jul  6 18:58:39 helium sshd[28455]: debug3: mm_request_send entering: type 47
Jul  6 18:58:39 helium sshd[28455]: Failed publickey for portfwd from 161.80.249.101 port 6710 ssh2

Note the 'User account has expired' message from PAM.  I get that
message on every account that tries to log in via ssh, even though
the accounts are fine.

I ran /etc/init.d/rmnologin-- no change.