From owner-freebsd-hackers  Sat Feb  8 06:15:42 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA13959
          for hackers-outgoing; Sat, 8 Feb 1997 06:15:42 -0800 (PST)
Received: from weenix.guru.org (kmitch@weenix.guru.org [198.82.200.65])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA13954
          for <hackers@freebsd.org>; Sat, 8 Feb 1997 06:15:36 -0800 (PST)
Received: (from kmitch@localhost)
	by weenix.guru.org (8.8.5/8.8.5) id JAA01180
	for hackers@freebsd.org; Sat, 8 Feb 1997 09:15:34 -0500 (EST)
From: Keith Mitchell <kmitch@weenix.guru.org>
Message-Id: <199702081415.JAA01180@weenix.guru.org>
Subject: User Classes in passwd
To: hackers@freebsd.org
Date: Sat, 8 Feb 1997 09:15:34 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL30 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I don't know if this was an oversight or not, but it looks like user classes
are implemented everywhere else so I thought I would mention it.

passwd currently doesn't look in the class database to reset a user's
password expiration time when they change their password.  In fact,
in local_password.c there is a comment saying that user classes will
change the default behavior of just setting the expire time to 0.