Thanks for the answer.
I want my program to determistically run on other computers as well,
thus I can't assume anything in advance about users' lua script. I had
not really thought about compiled plugins but that's the same issue,
these optional modules may alter the way my program expects tshark to
behave.
I believe for my usecase, the best is to wrap the tshark call with an
XDG_CONFIG_HOME pointing nowhere or to a vanilla wireshark config. Not
sure if there is any difficulty though, I will have a try.
Best regards
Matt
Le mar. 2 juil. 2019 à 12:15, Guy Harris <guy@xxxxxxxxxxxx> a écrit :
>
> On Jul 1, 2019, at 7:19 PM, Matt <mattator@xxxxxxxxx> wrote:
>
> > Lately I've been experimenting with the lua support (I had not
> > realized how fantastic it was, I am really looking forward to
> > implementing some of the options I wanted but couldn't upstream !).
> > The downside is that my lua scripts now interfere with a program that
> > launches tshark to generate a csv file of pcap.
>
> It sounds as if what you *really* need is to have one or more of *your scripts* disabled.
>
> This is not necessarily an issue specific to Lua scripts; a compiled plugin could cause similar problems.
>
> Perhaps we need an option to disable particular plugins by name in TShark and some GUI option to disable them in Wireshark.
>
> *If* your plugin (whether Lua or compiled) is a dissector, and it adds a *new* protocol, you should be able disable it with the --disable-protocol command-line option, specifying its protocol by name.
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives: https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
