From owner-freebsd-questions Sat Feb 20 19:11:29 1999 Delivered-To: freebsd-questions@freebsd.org Received: from kazos.net (jkazos.campus.vt.edu [198.82.109.110]) by hub.freebsd.org (Postfix) with SMTP id ADE5B10E0B for ; Sat, 20 Feb 1999 19:11:24 -0800 (PST) (envelope-from jkazos@usa.net) Received: from [198.82.109.110] ([198.82.109.110] verified) by kazos.net (Stalker SMTP Server 1.6) with ESMTP id S.0000003858 for ; Sat, 20 Feb 1999 22:11:23 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: jkazos@pop.netaddress.com Message-Id: In-Reply-To: <19990221011521.7175.qmail@alpha.comkey.com.au> References: <19990220181518.A7FF31183F@hub.freebsd.org> of Sat, 20 Feb 1999 16:15:15 -0200 <199902201754.MAA18691@hyperhost.net> <19990220181518.A7FF31183F@hub.freebsd.org> Date: Sat, 20 Feb 1999 22:11:21 -0500 To: freebsd-questions@FreeBSD.ORG From: "John Anthony Kazos Jr." Subject: Re: I've been hacked! Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An extremely cynical view, but one that's unfortunately applicable, correct, and heeded by the wisest. *sigh* >That's not a cut and dried conclusion. There are plenty of >cases of would-be crackers developing revenge obsessions against >people who retaliate. Unless you're willing to cope with this >and have the time and other resources needed to manage it, you >may find it a better option simply to concentrate on ensuring >that your machines are as secure as possible. This will most >likely encourage the cracker to look for an easier target. >After all, for most crackers, the number of failures is so high >that another one is not a big deal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message