Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] V1.0.0pre1 & MIB Files

From: "Keith French" <keithfrench@xxxxxxxxxxxxx>
Date: Sun, 23 Mar 2008 19:13:42 -0000
Jaap/Andrew,

So where do we go from here? These MIBs worked fine under Wireshark V0.99.6a (at least I think it was that version - it was the last one before the SNMP dissectors were redone).

Jaap though it could be bug 2253:-
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2253

Once that has been fixed I could retry it and then report it if is still not working?

Keith French.

----- Original Message ----- From: "Andrew Hood" <ajhood@xxxxxxxxx>
To: "Community support list for Wireshark" <wireshark-users@xxxxxxxxxxxxx>
Sent: Saturday, March 22, 2008 12:11 PM
Subject: Re: [Wireshark-users] V1.0.0pre1 & MIB Files


Jaap Keuter wrote:
Hi,

Frankly, I don't get warm fuzzy feelings with libraries which are to *support* our program and make it crash when fed bad data. Especially since the data is
not in our control (UAT configurable).
Bottom line: It should be fixed in the lib, not with (commandline) tools that
are alien to the users.

The inability of manufacturers to write syntactically correct MIBs is
legendary. Users also need to understand IMPORT clauses.

The switch to libsmi was a conscious decision on the part of one or more
Wireshark developers. I was one of those who suggested it, but having
been a long time libsmi user I knew it would require work to be
reliable, and was somewhat surprised at the speed in which it went into
the mainline.

NetSNMP "silently" ignores OIDs it can't resolve but has its problems
too. If compiled with OpenSSL it is liable to all the potential OpenSSL
vulnerabilities, and runs into issues with the difference between the
Wireshark, NetSNMP and OpenSSL licenses.

Most Linux systems will have NetSNMP installed, usually linked with
OpenSSL. Many other *nixes may have NetSNMP too, usually linked with
OpenSSL. You would need to statically link with a Wireshark provided
non-SSL version to avoid any such issues.

Today you have a choice. Switch back to NetSNMP, or contribute to libsmi
development to make it more usable in Wireshark.

--
There's no point in being grown up if you can't be childish sometimes.
               -- Dr. Who
_______________________________________________
Wireshark-users mailing list
Wireshark-users@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-users



--------------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG.
Version: 7.5.519 / Virus Database: 269.21.8/1339 - Release Date: 22/03/2008 16:43