From owner-freebsd-security  Wed Nov 11 10:23:34 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA16287
          for freebsd-security-outgoing; Wed, 11 Nov 1998 10:23:34 -0800 (PST)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from uucp.intac.com (uucp.intac.com [198.6.114.27])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16280
          for <freebsd-security@FreeBSD.Org>; Wed, 11 Nov 1998 10:23:29 -0800 (PST)
          (envelope-from oortiz@LCSI.COM)
From: oortiz@LCSI.COM
Received: (uucp@localhost) by uucp.intac.com (8.9.1/8.9.1 dman) with UUCP id MAA03296 for freebsd-security@FreeBSD.Org; Wed, 11 Nov 1998 12:55:48 -0500 (EST)
Received: from Connect2 Message Router by lcsi.LCSI.COM
           via Connect2-UUCP v1.00.34; Wed, 11 Nov 98 12:42:41 -0500
Message-Id: <3286493681000000@LCSI.COM>
Date: Wed, 11 Nov 98 12:33:03 -0500
Organization: LCS Industries
To: freebsd-security@FreeBSD.ORG
Subject: Intruder Lockout
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7BIT
X-Mailer: Connect2-UUCP v1.00.34
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

     
     Is there anyway to have an Intruder Lockout in FreeBSD? Like if 
     someone is trying to hack into my system with a certain user account, 
     and if after 3 to 5 attempts of typing in the wrong password, will the 
     system lock out the account instead of letting him try again like 
     Netware does?
     
     Many Thanks...

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message