Wireshark-dev: Re: [Wireshark-dev] What Wireshark base version to use for customization
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: "John Dill" <John.Dill@xxxxxxxxxxxxxxxxx>
Date: Wed, 10 Dec 2014 12:51:23 -0500
>Message: 2
>Date: Wed, 10 Dec 2014 15:13:08 +0000
>From: Anders Broman <anders.broman@xxxxxxxxxxxx>
>To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
>Subject: Re: [Wireshark-dev] What Wireshark base version to use for
>	customization
>Message-ID:
>	<43C5658BA3FB7B48A6F38EED0B6253F11AA7C45C@xxxxxxxxxxxxxxxxxxxxxx>
>Content-Type: text/plain; charset="utf-8"
>
>Hi,
>Note that under GPL you are obliged to supply the source code of your modifications if you distribute binaries to your customers.
>I would use the development version to get the bleeding edge stuff or the latest stable if stability is more of an issue.
>
>Regards
>Anders

So what restrictions are there when you have a Wireshark plugin that contains proprietary information (which can be of the do not export variety) from the govt or customer and they do *not* want that information released to the public, since Wireshark can be used as a tool to visualize and analyze these private kinds of protocols?  If some of that implementation leaks into the Wireshark application (like hiding all of the unnecessary protocol cruft to make it simpler for user to use), what are the implications?

Best Regards,
John D.

<<winmail.dat>>