From owner-freebsd-questions Thu Aug 24 08:10:29 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id IAA23763 for questions-outgoing; Thu, 24 Aug 1995 08:10:29 -0700 Received: from mpp.minn.net (mpp.Minn.Net [204.157.201.242]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id IAA23757 for ; Thu, 24 Aug 1995 08:10:26 -0700 Received: (from mpp@localhost) by mpp.minn.net (8.6.11/8.6.9) id KAA03556; Thu, 24 Aug 1995 10:12:14 -0500 From: Mike Pritchard Message-Id: <199508241512.KAA03556@mpp.minn.net> Subject: Re: Account expiration bug or feature? To: wollman@lcs.mit.edu (Garrett A. Wollman) Date: Thu, 24 Aug 1995 10:12:14 -0500 (CDT) Cc: peter@haywire.dialix.com, freebsd-questions@freebsd.org In-Reply-To: <9508222030.AA04882@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Aug 22, 95 04:30:43 pm X-Mailer: ELM [version 2.4 PL24 ME7a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 716 Sender: questions-owner@freebsd.org Precedence: bulk Garrett A. Wollman wrote: > > < > > Hmm.. > > > Perhaps a hook in getpwent() and friends? If the account is expired, > > perhaps return a fake pw_shell? > > Or much better, fix ftpd to check the expiration time. I thought it > already did... I have fixes for about 6 or 7 commands to properly support password expiration dates. I haven't commited it yet because one of the programs is "at", and I was waiting for the import problems with that to be cleaned up before commiting them. I'll probably get around to it this weekend. -- Mike Pritchard mpp@mpp.minn.net "Go that way. Really fast. If something gets in your way, turn"