On 02/01/2013 10:35 PM, Gerald Combs wrote:
Would anyone object to enabling silent build rules by default in
configure.ac (line 691)? It drastically reduces the amount of output
during compilation. For example
CC file.lo
replaces a screen full of text. You would still be able to
Hello folks,
I've developed a WhatsApp protocol dissector. Are you interested in
merging the plugin in wireshark source?
The plugin features packet dissection with decryption (only if the key
is known). It's still very basic but very useful for protocol
implementation and testing. I used it
Hi David,
That sounds like a pretty interesting dissector, to me. In order to
kick-start the contribution process, I recommend doing the following:
- Registering at http://bugs.wireshark.org
- Converting your code into a build-in dissector (a relatively trivial
process that involves
Yes David,
Tyson is right... that does sound like a pretty interesting dissector! Go
ahead !
On Sat, Feb 2, 2013 at 10:33 PM, Tyson Key tyson@gmail.com wrote:
Hi David,
That sounds like a pretty interesting dissector, to me. In order to
kick-start the contribution process, I recommend
On Feb 2, 2013, at 5:10 AM, Jaap Keuter jaap.keu...@xs4all.nl wrote:
On 02/01/2013 10:35 PM, Gerald Combs wrote:
Would anyone object to enabling silent build rules by default in
configure.ac (line 691)? It drastically reduces the amount of output
during compilation. For example
CC
Hello,
I am trying to create a new plugin and followed the steps as mentioned in
README.plugins. I am getting the following error when I am giving the make
command. I am doing it from Ubuntu 12.04
===
wireshark-1.8.0rc2$ make
Makefile:3857: *** commands commence before first target. Stop
==
