Wireshark mailing list archives
Thoughts on disabling an old dissector
From: Evan Huus <eapache () gmail com>
Date: Wed, 18 Dec 2013 13:33:00 -0500
This was originally filed as bug 9569. The situation is sufficiently unusual that I really don't know what the best solution is, so I figured I'd ask for general comments from the list. The company who created and used the TPNCP protocol (and submitted the packet-tpncp.c dissector) wants to reuse that name for a new, different protocol and are asking us to disable the old dissector to avoid conflicts. The bug has more detail. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9569 Thoughts? ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Thoughts on disabling an old dissector Evan Huus (Dec 18)
- Re: Thoughts on disabling an old dissector Joerg Mayer (Dec 18)
- Re: Thoughts on disabling an old dissector Michael Lum (Dec 18)
- Re: Thoughts on disabling an old dissector Tyson Key (Dec 18)
- Re: Thoughts on disabling an old dissector Christopher Maynard (Dec 18)
- Re: Thoughts on disabling an old dissector ronnie sahlberg (Dec 18)
- Re: Thoughts on disabling an old dissector Joerg Mayer (Dec 18)