[45864] in North American Network Operators' Group
Re: Maformed SNMP Packet log/trace
daemon@ATHENA.MIT.EDU (Sean Donelan)
Tue Feb 26 18:42:15 2002
Date: Tue, 26 Feb 2002 18:41:22 -0500 (EST)
From: Sean Donelan <sean@donelan.com>
To: Eric Brandwine <ericb@UU.NET>
Cc: Brennan_Murphy@NAI.com, <nanog@merit.edu>
In-Reply-To: <gu9d6yscb0w.fsf@rampart.argfrp.us.uu.net>
Message-ID: <Pine.GSO.4.40.0202261834130.3454-100000@clifden.donelan.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
On 26 Feb 2002, Eric Brandwine wrote:
> Go to the Oulu University page mentioned in the advisory.
>
> Download the 4 .jar files that comprise the toolkit.
>
> unzip the jar files. There'll be a testcases/ dir in each of them.
> Each file in this directory is one of their packets.
>
> There are 53,000 of them. Have fun!
And to keep things exciting, programmers rarely make mistakes in
only one protocol. Turing still holds. It wouldn't be surprising
if other packets can do bad things when "this should never happen"
happens. Who is checking NTP, OSPF, ISIS, BGP, SSH, DNS, TELNET,
TACACS+, etc code paths?
