From owner-freebsd-security Wed May 5 14:45:46 1999 Delivered-To: freebsd-security@freebsd.org Received: from angel.double-barrel.be (mail.double-barrel.be [194.7.102.22]) by hub.freebsd.org (Postfix) with ESMTP id 5884F14BE7 for ; Wed, 5 May 1999 14:45:37 -0700 (PDT) (envelope-from mvergall@double-barrel.be) Received: from double-barrel.be (ws1.double-barrel.be [194.7.102.29]) by angel.double-barrel.be (8.9.1b+Sun/8.9.1) with ESMTP id XAA01516; Wed, 5 May 1999 23:44:51 +0200 (MET DST) Message-ID: <3730BC13.9EA40ED9@double-barrel.be> Date: Wed, 05 May 1999 23:45:55 +0200 From: "Michael C. Vergallen" X-Mailer: Mozilla 4.51 [en] (X11; I; SunOS 5.7 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: CyberPsychotic Cc: freebsd-security@freebsd.org, "Michael C. Vergallen" Subject: Re: FreeBSD 3.1 remote reboot exploit (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org CyberPsychotic wrote: > hmm.. depends on how you did that. Assuming from the other reports people > send to the list, I believe the problem appears on tcp/ip level _maybe_ with > some specific kernel options turned on. I've played with a friend's of mine > machine bombing it with various sorts of maliformed tcp/udp and just sick ip > datagrams but wasn't able to reproduce this. If anyone expirienced the > problem wouldn't mind to share their log files/network traffic dump, I would > appreciate that. I 've been genrating packets of different sizes and only ones have I managed to lock the box up while transfering a 1 GB image file and pulling the cable to the disc-crate by accident. Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message