From owner-freebsd-security Sun Jan 23 19:46:15 2000 Delivered-To: freebsd-security@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1013B14C89 for ; Sun, 23 Jan 2000 19:46:10 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA98458; Sun, 23 Jan 2000 20:45:57 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA48819; Sun, 23 Jan 2000 20:46:30 -0700 (MST) Message-Id: <200001240346.UAA48819@harmony.village.org> To: Wes Peters Subject: Re: stream.c Cc: Alfred Perlstein , Richard Steenbergen , freebsd-security@FreeBSD.ORG In-reply-to: Your message of "Sun, 23 Jan 2000 20:23:06 MST." <388BC59A.1AD012C5@softweyr.com> References: <388BC59A.1AD012C5@softweyr.com> <20000123102829.C18349@above.net> <20000123083234.N26520@fw.wintelcom.net> Date: Sun, 23 Jan 2000 20:46:30 -0700 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <388BC59A.1AD012C5@softweyr.com> Wes Peters writes: : You're fixing the wrong problem. The problem stems from injecting multicast : RST packets, which generate multicast replies on all attached interfaces. : The real solution seems to be to reject the invalid multicast TCP packets : without generating a reply, since they cannot possibly be valid packets. That's one of the two parts of the patch that I'm working on. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message