From owner-freebsd-questions@FreeBSD.ORG Sun Aug 28 02:28:43 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8A6E16A41F for ; Sun, 28 Aug 2005 02:28:43 +0000 (GMT) (envelope-from freebsd-questions@auscert.org.au) Received: from titania.auscert.org.au (gw.auscert.org.au [203.5.112.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3A3C43D45 for ; Sun, 28 Aug 2005 02:28:42 +0000 (GMT) (envelope-from freebsd-questions@auscert.org.au) Received: from app.auscert.org.au (app [10.0.1.192]) by titania.auscert.org.au (8.12.10/8.12.10) with ESMTP id j7S2SYqA017874; Sun, 28 Aug 2005 12:28:34 +1000 (EST) Received: from app.auscert.org.au (localhost.auscert.org.au [127.0.0.1]) by app.auscert.org.au (8.13.1/8.13.1) with ESMTP id j7S2Sfx0052319; Sun, 28 Aug 2005 12:28:41 +1000 (EST) (envelope-from freebsd-questions@auscert.org.au) Message-Id: <200508280228.j7S2Sfx0052319@app.auscert.org.au> To: freebsd-questions@freebsd.org from: freebsd-questions@auscert.org.au In-Reply-To: Your message of "Sat, 27 Aug 2005 20:37:40 -0400." <43110754.6010608@nawcom.no-ip.com> Date: Sun, 28 Aug 2005 12:28:41 +1000 Cc: nawcom Subject: Re: Illegal access attempt - FreeBSD 5.4 Release - please advise X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 02:28:43 -0000 > if this server was used by 100+ people i would of course not have such a > harsh security script set up. everyone who uses it has great experience > and understands the consequences. like i said before, this is usually > for personal use and has about 12 users total. if this was used to > manage ssh on something big i would lower the security measures. > > hope you can understand some now :) Certainly. However, given that you are willing to accept (risk?) 5 attempts at a legitimate account I don't believe there would be any greater risk in allowing the same for invalid accounts also, given that the likelihood of gaining access to those is actually less - and it would make your script simpler, too, whilst preventing the (albeit, unlikely in your situation) possibility of a DoS to a valid user. To be honest, reversing your logic somewhat wrt valid/invalid accounts and 1/5 attempts could have merit also. That said, I'd be interested in seeing how you implement this with swatch as I'm looking at log parsing solutions in general. best regards, -- Joel Hatton -- Security Analyst | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert@auscert.org.au