From owner-freebsd-security Tue Oct 27 00:22:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24744 for freebsd-security-outgoing; Tue, 27 Oct 1998 00:22:28 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24739 for ; Tue, 27 Oct 1998 00:22:25 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id SAA01732; Tue, 27 Oct 1998 18:51:45 +1030 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA12217; Tue, 27 Oct 1998 18:51:44 +1030 Date: Tue, 27 Oct 1998 18:51:44 +1030 (CST) From: Kris Kennaway To: Fedor Gubarev Cc: freebsd-security@FreeBSD.ORG Subject: Re: nestea v2 against freebsd 3.0-Release 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 Tue, 27 Oct 1998, Fedor Gubarev wrote: > I wonder why there is no response at all on this mail. > It seems a little bit surprising at least..... I forwarded your mail to -current the other day after I verified the problem, since thats where most of the developers hang out, and the answer is that it's a bug for which a patch is under consideration for committing (unless I misunderstood Don Lewis's message, it's a legitimate vulnerability in the networking code). Presumably a security advisory will be issued once the fix is available and tested. If you need to patch this immediately, I can forward you a copy of the latest proposed patch I've seen, which might however have other unforseen consequences (i.e. it's not "official"). Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message