From owner-freebsd-security Fri Jan 21 3:20: 0 2000 Delivered-To: freebsd-security@freebsd.org Received: from ns1.via-net-works.net.ar (ns1.via-net-works.net.ar [200.10.100.10]) by hub.freebsd.org (Postfix) with ESMTP id 67D4815458 for ; Fri, 21 Jan 2000 03:19:57 -0800 (PST) (envelope-from fpscha@ns1.via-net-works.net.ar) Received: (from fpscha@localhost) by ns1.via-net-works.net.ar (8.9.3/8.9.3) id IAA15446; Fri, 21 Jan 2000 08:20:11 -0300 (GMT) From: Fernando Schapachnik Message-Id: <200001211120.IAA15446@ns1.via-net-works.net.ar> Subject: Re: bugtraq posts: stream.c - new FreeBSD exploit? In-Reply-To: <000101bf63e9$76352f30$01000000@madman> from Bob Madden at "Jan 21, 0 02:28:10 am" To: bobm@atgsystems.com (Bob Madden) Date: Fri, 21 Jan 2000 08:20:10 -0300 (GMT) Cc: freebsd-security@FreeBSD.ORG Reply-To: Fernando Schapachnik X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone tried stream.c against CISCO, Nortel, etc. routers? Althoug off-topic, their (unofficial) vulnerability status would be very helpfull? TIA! En un mensaje anterior, Bob Madden escribió: > I'm grateful for the efforts put forth in finding a reliable means of > prevention to this attack. I have seen it's effects. For the benefit of those > working on the solution, I wanted to share what I see when the attack is in > full swing: Fernando P. Schapachnik Administración de la red VIA NET.WORKS ARGENTINA S.A. fernando@via-net-works.net.ar (54-11) 4323-3333 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message