Bug 25586

Summary: Password expiration doesn't work after upgrade of system
Product: Base System Reporter: Przemyslaw Frasunek <venglin>
Component: binAssignee: Brian Feldman <green>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.2-STABLE   
Hardware: Any   
OS: Any   

Description Przemyslaw Frasunek 2001-03-07 10:40:01 UTC 
	If password is expired, sshd enters in infinite loop flooding
	syslog with such messages and eating all CPU time.

Mar  7 11:25:31 yeti sshd[43628]: PAM pam_chauthtok failed[6]: Permission denied
Mar  7 11:25:31 yeti sshd[43628]: no modules loaded for `sshd' service

	The normal behaviour was to spawn passwd and allow user to change the
	password.

Fix: 

Unknown.
How-To-Repeat: 
	Turn on password expiration, login on account with expired password.
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2001-03-24 05:42:59 UTC 
Responsible Changed
From-To: freebsd-bugs->green

Not sure if this is a PAM problem or an OpenSSH problem, but 
punt it to green on the assumption it's the latter
Comment 2 smkelly 2001-08-01 03:00:09 UTC 
bin/25586 describes a problem with users using SSH to access the system
after their password has expired.  I've recently experienced the exact
same problem.  Users with expired passwords cause the following to pour
into syslog until the user disconnects their client:

sshd[43628]: PAM pam_chauthtok failed[6]: Permission denied
sshd[43628]: no modules loaded for `sshd' service

My pam.conf is identical to /usr/src/etc/pam.conf.

Further investigation shows that this only happens when the user is
using SSH protocol 2 to access the system.  A user with an expired
password is able to reset it normally if they are using a SSH1 client
to access the system.  Use of SSH2 is what causes the errors.

As of this moment, the reason for this is beyond me.

-- 
Sean Kelly         | PGP KeyID: 77042C7B
smkelly@zombie.org | http://www.zombie.org

For PGP key, send e-mail with subject "send pgp key"
Comment 3 perisa 2002-05-29 01:58:51 UTC 
Hi,

does this problem still exists in a recent FreeBSD 4-STABLE system?

Thanks

Marc
Comment 4 Brian Feldman freebsd_committer freebsd_triage 2003-07-13 05:15:36 UTC 
State Changed
From-To: open->closed

Obsolete.