From owner-freebsd-security Mon Mar 19 23:22:23 2001 Delivered-To: freebsd-security@freebsd.org Received: from lariat.org (lariat.org [12.23.109.2]) by hub.freebsd.org (Postfix) with ESMTP id B085237B719 for ; Mon, 19 Mar 2001 23:22:20 -0800 (PST) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp0.lariat.org@lariat.org [12.23.109.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id AAA20030; Tue, 20 Mar 2001 00:19:34 -0700 (MST) Message-Id: <4.3.2.7.2.20010320001710.00d88950@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 20 Mar 2001 00:19:15 -0700 To: Kris Kennaway From: Brett Glass Subject: Re: Odd event -- possible security hole or DoS? Cc: security@freebsd.org In-Reply-To: <20010319223615.B14837@xor.obsecurity.org> References: <4.3.2.7.2.20010319172800.00cf9c60@localhost> <4.3.2.7.2.20010319172800.00cf9c60@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:36 PM 3/19/2001, Kris Kennaway wrote: >I can't even begin to remember all of the TCP, kernel and application >bugs fixed in the 2 1/2 years since 2.2.8. There are probably a >number of ways someone could have caused something like this. I guess what I'm concerned about is that I don't know if it's an intentional DoS and/or if it's present in current versions. I'll try to do some testing to see if I can lock up inetd on that system again via finger. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message