Re: Publishing binaries for a new plugin

[Raúl Kripalani <raul.kripalani () consensys net>]

Hi Graham,

I indeed intend to submit the dissector for inclusion in the Wireshark
distribution at a later stage, once it’s tested by the community, stable
and feature-complete.

In the meantime, some pointers w.r.t. to my immediate issue would be great.
Perhaps this is a 2.6.2 (unreleased) vs. 2.6.1 compatibility issue, as
plugins built with the former are recognised but not activated in the
latter?

Cheers.

On Thu, 21 Jun 2018 at 22:34, Graham Bloice <graham.bloice () trihedral com>
wrote:

> On Thu, 21 Jun 2018 at 20:02, Raúl Kripalani <raul.kripalani () consensys net>
> wrote:
>
> > Hello,
> >
> > We’ve built a Wireshark dissector plugin for Ethereum devp2p protocols,
> > and we’re preparing it to publish it on Github shortly. We want to offer
> > precompiled .so and .dll downloads, so that users can place them in their
> > plugins directory for an easy start.
> >
> > I’m running on Mac OS X 10.13.4, and using a Ninja build against
> > master-2.6. It generates the application binary properly (Wireshark.app)
> > and places the plugin .so under the bundled
> > Contents/PlugIns/wireshark/2.6/epan directory of the bundle.
> >
> > However, if I extract the file manually and place it inside the
> > Wireshark.app package of a downloaded version (2.6.1) (simulating what a
> > user would do), the plugin gets recognised in the About > Plugins pane, but
> > there are no signs of the dissector, nor the menu points for the SRT table,
> > statistics table, etc. anywhere in the UI.
> >
> > If I replace the .so of other plugins like ethercat, gryphon, etc. in
> > downloaded distribution with the ones generated from my build, the same
> > thing happens.
> >
> > May someone point me to what might be happening here?
> >
> > Thank you,
> > Raúl.
>
> Not necessarily the answer you're looking for, but if you submit your
> dissector to the Wireshark project then we'll maintain (w.r.t. the rest of
> the Wireshark infrastructure) and distribute the dissector for you.  Users
> would also not have to handle downloading and installing the correct plugin
> binary for their specific version of Wireshark.
>
> We would prefer a built-in dissector.  See the Wiki page on Creating
> Patches for more info: https://wiki.wireshark.org/CreatingPatches.
>
> --
> Graham Bloice
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark org
> ?subject=unsubscribe

-- 

*Raúl KripalaniProtocol Engineering Groups and Systems (PegaSys) *
raul.kripalani () consensys net | +34 679 52 41 75
Web <https://consensys.net/> | Twitter <https://twitter.com/raulvk> |
LinkedIn <https://www.linkedin.com/in/raulkripalani/>

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe