Date: Tue, 18 Mar 2003 23:11:20 +0100 From: des@ofug.org (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) To: Julian Elischer <julian@elischer.org> Cc: re@freebsd.org, hackers@freebsd.org Subject: Re: rumour of password aging failure in 4.7/4.8RC Message-ID: <xzp3clk2ulz.fsf@flood.ping.uio.no> In-Reply-To: <Pine.BSF.4.21.0303181250540.79971-100000@InterJet.elischer.org> (Julian Elischer's message of "Tue, 18 Mar 2003 13:33:31 -0800 (PST)") References: <Pine.BSF.4.21.0303181250540.79971-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer <julian@elischer.org> writes: > I've received a few reports from teh field that password aging > with ssh in 4.7 and 4.8RC is broken. Recent versions of OpenSSH do not support prompting the user for a new password. I haven't tested it, but I think users with expired passwords will simply be locked out. > Is there anyone out there that is using passwork expiry=20 > and ssh? Who's the expert? In the FreeBSD community, that would be me. > How does PAM come into this? It doesn't, really. It's a privsep problem + the fact that some of the pertinent code has been disabled and / or left unimplemented because it wouldn't work with privsep (so turning privsep off won't help). DES --=20 Dag-Erling Sm=F8rgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp3clk2ulz.fsf>
