From owner-freebsd-stable Tue Jul 14 10:56:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10431 for freebsd-stable-outgoing; Tue, 14 Jul 1998 10:56:26 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA10422 for ; Tue, 14 Jul 1998 10:56:25 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yw9It-0004qd-00; Tue, 14 Jul 1998 10:55:51 -0700 Date: Tue, 14 Jul 1998 10:55:49 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Wes Peters cc: paulo@nlink.com.br, jer@jorsm.com, freebsd-stable@FreeBSD.ORG Subject: Re: Finger and getpwent In-Reply-To: <199807140513.XAA13051@obie.softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Jul 1998, Wes Peters wrote: > A *somewhat* better solution is to use my nologin program, which logs > attempts to login to disabled accounts via syslog. You can retrieve Except that nologin just stops shell logins, not all password authentication. So POP, IMAP, some FTP, RADIUS, all suceed. Munging the password field is better. Attempts to access disabled accounts is logged as well, as will all incorrect passwords. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message