Brian,
The GPL does not extend itself beyond your Wireshark dissector, but whether you release your dissector to be included in Wireshark someday or use it only for your clients, it is still covered under the terms of the GPL. As far as any Wireshark dissectors are concerned, they are all GPL'd no matter what. Whatever other software you distribute to your customers has nothing to do with your Wireshark dissector so you are free to use whatever license you want for that, but the Wireshark dissectors must be GPL'd. I'm not sure you understand this.
BTW, I (and many others I'm sure), are in the same boat as you. I've written many Wireshark dissectors for my company, none of which have been released outside of my company because the protocols they dissect are all proprietary. The dissectors are thus used internally only and therefore the source code need not be made available to anyone outside our organization. This concept is covered in brevity here: http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic. However, that said, the dissectors I've written are still covered under the GPL per http://www.gnu.org/licenses/gpl-faq.html#GPLModuleLicense. I do not wish to write my own proprietary protocol analyzer so I happily accept the terms of the GPL.
- Chris
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Brian Oleksa
Sent: Tuesday, March 23, 2010 11:42 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Packet Size limited during capture message
Chris
I will have to look into why my dissector is crashing when I get the Packet Size Limited during capture message.
I am an employee of Dark Corner Software. I am writing the dissector for our clients that use our software.
I have fixed the license issue. Attached is the latest updated file that I am still working on.
We have open source software and closed source software. I am trying to get the open source dissector submitted through wireshark so it can become a part of the wireshark distribution (this is the attached copy).
Our closed source software is for our customers only. I have written a dissector for our closed source software for the client. This is where I am getting the "Packet Size limited during capture " message from.
Thanks,
Brian
Maynard, Chris wrote:
> As Jakub pointed out, regardless of the snaplen, if Wireshark is crashing, then the bug is in the dissector, although IMO the biggest bug in the dissector is still the incompatible license.
>
> Brian, please carefully read
> http://www.gnu.org/licenses/gpl-faq.html#GPLModuleLicense
>
> Gerald et al, consider this e-mail as a report of a violation of the
> GPL per http://www.gnu.org/licenses/gpl-faq.html#ReportingViolation
>
> So until the dissector is properly licensed, I suggest contacting
> these folks for support on this dissector:
> http://www.darkcornersoftware.com/contact.html
>
> - Chris
>
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Mike Morrin
> Sent: Tuesday, March 23, 2010 9:02 AM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Packet Size limited during capture
> message
>
>
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Brian Oleksa
> Sent: 23 March 2010 12:23
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Packet Size limited during capture
> message
>
> Chris
>
> I just found out that this was captured using tshark.....but nobody
> knows what the snaplen was.
>
> So my questions is.... My code is working correctly then....And that
> this was just a bad judgment of the wrong snaplen......correct..??
>
> Thanks,
> Brian
>
> --------------------------------------------------------------------
> It is possible for a dissector bug to throw this exception even with a
> perfectly captured packet, see Bug 2855 for example.
>
>
>
>
>
>
>
> This message contains confidential information and may be privileged. If you are not the intended recipient, please notify the sender and delete the message immediately.
>
> ip.access Ltd, registration number 3400157, Building 2020, Cambourne
> Business Park, Cambourne, Cambridge CB23 6DW, United Kingdom
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
> CONFIDENTIALITY NOTICE: The contents of this email are confidential
> and for the exclusive use of the intended recipient. If you receive
> this email in error, please delete it from your system immediately and
> notify us either by email, telephone or fax. You should not copy,
> forward, or otherwise disclose the content of the email.
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.
