From owner-freebsd-security Fri Oct 16 10:07:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24550 for freebsd-security-outgoing; Fri, 16 Oct 1998 10:07:09 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from mercury.jorsm.com (mercury.jorsm.com [207.112.128.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24545 for ; Fri, 16 Oct 1998 10:07:07 -0700 (PDT) (envelope-from jer@jorsm.com) Received: from localhost (jer@localhost) by mercury.jorsm.com (8.8.7/8.8.7) with SMTP id MAA18345; Fri, 16 Oct 1998 12:06:39 -0500 (CDT) Date: Fri, 16 Oct 1998 12:06:38 -0500 (CDT) From: Jeremy Shaffner To: Liam Slusser cc: security@FreeBSD.ORG Subject: Re: smurf and broadcast packets.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 14 Sep 1998, Liam Slusser wrote: > > Today my server was bombed by a smurf attack. After i got everthing up > > What am i doing wrong? What can i do to stop my server from being the > victom of another smurf attack? > I know this is a bit old, but it wasn't your network that was exploited, it was someone elses. Yours was the target. Patching yourself only prevents your network from being used to launch an attack against someone else. -===================================================================- Jeremy Shaffner JORSM Internet Senior Technical Support Northwest Indiana's Premium jer@jorsm.com Internet Service Provider support@jorsm.com http://www.jorsm.com -===================================================================- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message