Wireshark mailing list archives
Re: Verification of user when running Wireshark
From: Jaap Keuter <jaap.keuter () xs4all nl>
Date: Tue, 19 Oct 2010 10:59:53 +0200
On 19 okt. 2010, at 08:53, Guy Harris <guy () alum mit edu> wrote:
On Oct 18, 2010, at 10:01 PM, Jaap Keuter wrote:Guy is right, the GPL voids this approach. Any Wireshark API call from your dissector makes it applicable, and I can't envision a plugin without one. You do have proto_mark_private() which limits exposure of your plugin, by blocking Wiki access for your protocol fields....not that, if your protocol is private, you should have any documentation of it in the (public!) Wireshark Wiki anyway, so that's more of a UI politeness feature than a protection feature (after all, somebody could just build a version of Wireshark with proto_mark_private() stubbed out).
Of course it's not a prevention on distribution of the code itself, but plugs a possible information leak when a careless user likes to create wiki entries. Any layer of information protection may be beneficial to help convince "the management" to support Wireshark use and development. Thanks, Jaap ___________________________________________________________________________ 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:
- Verification of user when running Wireshark Alex Lindberg (Oct 18)
- Re: Verification of user when running Wireshark Guy Harris (Oct 18)
- Re: Verification of user when running Wireshark Jaap Keuter (Oct 18)
- Re: Verification of user when running Wireshark Guy Harris (Oct 18)
- Re: Verification of user when running Wireshark Jaap Keuter (Oct 19)
- Re: Verification of user when running Wireshark Jaap Keuter (Oct 18)
- Re: Verification of user when running Wireshark Guy Harris (Oct 18)