From owner-freebsd-questions Wed Sep 3 18:38:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA23267 for questions-outgoing; Wed, 3 Sep 1997 18:38:32 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA23260 for ; Wed, 3 Sep 1997 18:38:27 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id CAA18293; Thu, 4 Sep 1997 02:38:09 +0100 (BST) Message-Id: <199709040138.CAA18293@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Matthew Hunt cc: Brian Somers , Bill Ott , freebsd-questions@FreeBSD.ORG Subject: Re: Password Aging In-reply-to: Your message of "Wed, 03 Sep 1997 21:27:52 EDT." <19970903212752.11772@mph124.rh.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Sep 1997 02:38:09 +0100 From: Brian Somers Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Thu, Sep 04, 1997 at 01:36:00AM +0100, Brian Somers wrote: > > > > Is there a nice clean (read easy) way to automate the expiration of user > > > passwords every 'x' days? I could right a script, but why re-invent the > > > wheel... > > > > Run ``chpass'' as root. > > As far as I can tell, you can set an expiry date, such as January 1, 1998, > but you can't say that the user's password expires every 90 days. > I think the latter is what the original poster wanted. > > If chpass has this functionality, I haven't managed to find it. You're right. I assumed that the ``change'' field did this - I expected it to be specified as a repeating period in days after the expire date. Oh well. > -- > Matthew Hunt * Think locally, act globally. > finger hunt@mph124.rh.psu.edu for PGP public key. -- Brian , Don't _EVER_ lose your sense of humour....