Date: Tue, 5 Aug 2003 08:25:42 -0700 From: David Schultz <das@freebsd.org> To: Mats Larsson <myrslok@sko.mh.se> Cc: des@freebsd.org Subject: Re: warnpassword and warnexpire in 5.1 login.conf Message-ID: <20030805152542.GA752@HAL9000.homeunix.com> In-Reply-To: <20030805122042.T55344@marvin.sko.mh.se> References: <20030802150826.D35850@marvin.sko.mh.se> <20030804061719.GB873@HAL9000.homeunix.com> <20030805122042.T55344@marvin.sko.mh.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 05, 2003, Mats Larsson wrote: > Sure, run cap_mkdb on every edit on login.conf > > The values im trying to use there are the following: > :warnexpire=28d:\ > :warnpassword=14d:\ > > And with pw i use the following to test with: (also with -e option) > pw usermod user -p +10d > > The only thing im getting now is i warning in messages when i try to login > into a locked account. > > Aug 5 12:14:39 marvin sshd[55256]: error: PAM: user accound has expired This looks reasonable. > And the following varning when password is old: > Aug 5 12:27:38 marvin sshd[55386]: error: PAM: OK > Aug 5 12:27:40 marvin sshd[55390]: fatal: PAM: chauthtok not supprted with privsep > > Is there perhaps a better PAM way of doing this things now?? Hmm... Apparently you can't change an expired password with a privilege-separated OpenSSH. I don't know whether that can be fixed, but perhaps des@ has some insight.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030805152542.GA752>