From owner-freebsd-questions Fri Apr 11 16:57:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA01188 for questions-outgoing; Fri, 11 Apr 1997 16:57:30 -0700 (PDT) Received: from mixcom.mixcom.com (mixcom.mixcom.com [198.137.186.100]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA01177 for ; Fri, 11 Apr 1997 16:57:20 -0700 (PDT) Received: by mixcom.mixcom.com (8.6.12/2.2) id SAA04520; Fri, 11 Apr 1997 18:57:56 -0500 Received: from p75.mixcom.com(198.137.186.25) by mixcom.mixcom.com via smap (V1.3) id sma004509; Fri Apr 11 23:57:41 1997 Message-Id: <3.0.32.19970411185027.00b70ac0@mixcom.com> X-Sender: sysop@mixcom.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 11 Apr 1997 18:50:27 -0500 To: tony@warp.co.uk From: "Jeffrey J. Mountin" Subject: Re: Death Ping & 2.1.7.1R Cc: freebsd-questions@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 05:58 PM 4/11/97 +0000, Anthony Barlow wrote: >I'm a little concerned with the problems people have been experiancing with >SCSI on FBSD 2.2.1R. Is 2.1.7.1R suceptable to the 'death ping' I recall in >an early message that 2.2.1 wasn't. Any system will be effected, especially if it is a flood. There is no real way to protect from a denial of service, but a system is considered vulernable if a large packet ping causes abnormal behaviour. Check out: http://www.sophist.demon.co.uk/ping/ and CERT advisory CA-96.26 for info. Interestingly the CERT says that 2.1.6 and -current were not vulnerable, but the Ping o' Death page states 2.1.0 and up. ------------------------------------------- Jeff Mountin - System/Network Administrator jeff@mixcom.net MIX Communications Serving the Internet since 1990