Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 9926] New: enhancement request - Cannot get wireshark's pl

Date: Tue, 25 Mar 2014 23:02:39 +0000
Bug ID 9926
Summary enhancement request - Cannot get wireshark's plugins path with lua.
Classification Unclassified
Product Wireshark
Version unspecified
Hardware x86
OS All
Status UNCONFIRMED
Severity Normal
Priority Low
Component Common utilities (libwsutil)
Assignee [email protected]
Reporter [email protected]

Build Information:
$ wireshark -v
wireshark 1.11.3 (wireshark-1.11.3-rc1-2076-gda83ead from master)

Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 2.24.22, with Cairo 1.13.1, with Pango 1.36.1, with
GLib 2.38.2, with libpcap, with libz 1.2.8, without POSIX capabilities, without
libnl, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, without Python, with
GnuTLS 3.1.20, with Gcrypt 1.5.3, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Aug  4 2013 06:59:20), with AirPcap.

Running on Linux 3.13.6-200.fc20.x86_64, with locale en_US.UTF-8, with libpcap
version 1.5.3, with libz 1.2.8, GnuTLS 3.1.20, Gcrypt 1.5.3, without AirPcap.
       Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz

Built using gcc 4.8.2 20131212 (Red Hat 4.8.2-7).

--
According to [1], there are no function to get the global plugins path[2] with
lua, nevertheless there are persconffile_path([filename]) and
datafile_path([filename]). I want to share the script with others, but due to
no function to get the path, I cannot do it simple way and good portability.

*eg)  /usr/local/lib/wireshark/plugins/1.11.3

I have submited a question about this, please see also [2].

[1] http://wiki.wireshark.org/LuaAPI/Utils
[2] http://www.wireshark.org/lists/wireshark-dev/201403/msg00176.html


You are receiving this mail because:
  • You are watching all bug changes.