Wireshark · Wireshark-dev: Re: [Wireshark-dev] Publishing binaries for a new plugin

[Graham Bloice <graham.bloice@xxxxxxxxxxxxx>]

On Thu, 21 Jun 2018 at 20:02, Raúl Kripalani <raul.kripalani@xxxxxxxxxxxxx> 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