Home page logo
/
wireshark logo
Wireshark Mailing List

Discussion of the free and open source Wireshark network sniffer. No other sniffer (commercial or otherwise) comes close. This archive combines the Wireshark announcement, users, and developers mailing lists.

List Archives

JanFebMarAprMayJunJulAugSepOctNovDec
20142903252752861533192776
2013230281375333280295279323271330289311
2012394261260268323308358365303353204213
2011434349425449414462615765363432361261
2010664572679696726480510521517495389343
2009550538370

Latest Posts

Re: [Wireshark-commits] master 43a81b6: Add some information on running from the build directory. Evan Huus (Aug 01)
Name resolution and lua failures are both due to the out-of-tree build.

Re: [Wireshark-announce] Wireshark 1.12.0rc3 is now available Graham Bloice (Aug 01)
The x86 CMake build now completes :-)

The x64 build is failing due to the lack of an acceptable Python and some
dumpcap link errors.

Re: [Wireshark-commits] master 43a81b6: Add some information on running from the build directory. Peter Wu (Aug 01)
Which part exactly? I can run most of the test-suite with an OOT build using:

WS_BIN_PATH=/tmp/wsbuild/run ./test.sh -s $suite

Some things fail for me, but that seems unrelated to the build dir:

clopts testing because unprivileged users still have a dbus capture interface)
2.4.1 Step: Invalid permissions for dumpcap parameter -D, exit status must be
2...

Re: [Wireshark-commits] master 43a81b6: Add some information on running from the build directory. Peter Wu (Aug 01)
[..]

The binaries themselves already Just Work(tm) without libtool because CMake
sets RPATH. (If it still tries to search for globally installed WS, note that
there existed a bug in CMake 2.8[1] that set the wrong RPATH when linked
against libraries in `/lib64`. That got fixed in CMake 3.0)

[1]: http://www.cmake.org/Bug/view.php?id=14875

That was indeed the reason for comments on security reasons, together with
ignoring plugins from the...

Re: [Wireshark-commits] master 7f3d97c: Include the gnm dissector. Anders Broman (Aug 01)
Den 1 aug 2014 01:23 skrev "Guy Harris" <guy () alum mit edu>:

wrote:

I created the dissector while doing other ITU asn1 dissectors in the hope
it would be useful, I have never seen a trace whit it or seen a bug report
so I removed it from the makefile but left the files to give a grace period
before removing it completely.

The same reasoning goes for the asn1 plugin. If it were to be still used
ideally it should be rewritten...

Re: [Wireshark-commits] master 43a81b6: Add some information on running from the build directory. Evan Huus (Aug 01)
FWIW this issue also makes it impossible to run parts of the test suite
from an out-of-tree build, which can be problematic.

Re: [Wireshark-commits] master 43a81b6: Add some information on running from the build directory. Guy Harris (Jul 31)
So that you can just type "./wireshark" or "./tshark" after you've done a build, and have it Just Work, rather than
having to install Wireshark or TShark before you can run it. Note that we run TShark to generate some man pages.

/*
* Check whether WIRESHARK_RUN_FROM_BUILD_DIRECTORY is set in the
* environment; if so, set running_in_build_directory_flag if we
* weren't started with special...

Re: [Wireshark-announce] Wireshark 1.12.0rc3 is now available Gerald Combs (Jul 31)
Done.

The machine has the official Python 2.6 installed in c:\Python26 and
Cygwin's Python 2.7 installed in c:\cygwin\usr\bin. According to

http://www.cmake.org/pipermail/cmake/2010-February/035404.html

CMake looks for numbered Pythons executables (python2.7, python2.6, ...)
before looking for the plain executable. In our case this means it's
finding Cygwin's Python before the official version. The version
detection then fails...

Re: [Wireshark-commits] master 7f3d97c: Include the gnm dissector. Guy Harris (Jul 31)
"Never used" in what sense?

Nobody ever read a capture file that used it?

Or nothing will ever use the OIDs for which it registers?

Re: Wireshark 1.12.0 is now available Guy Harris (Jul 31)
The source is still in the source tree; should we get rid of it?

It's still in the source tree, and I made the 1.99.0 autofoo and nmake builds, at least, use it.

If it's considered useful, we should build it.

If it's not considered useful, we should presumably get rid of it from the source tree.

So are the *BSDs "Linux" or "Unix"? :-)

I see the UN*Xes we support falling into these groups:

1) most...

Re: [Wireshark-commits] master 7f3d97c: Include the gnm dissector. Jeff Morriss (Jul 31)
This reverts r54561/b22d9ab940489f615c3968678a0d01df589d3045

(and only partially: the dissector is still removed from cmake.)

The commit message there says it was removed because it was never used.

(I noticed this only because the release notes for 1.12.0 point out that
the dissector was removed.)

Re: [Wireshark-commits] master 43a81b6: Add some information on running from the build directory. Peter Wu (Jul 31)
Oh my, that filesystem.c code is really ugly and relying on a lot of
assumptions. Why does it need to distinguish build dirs from other dirs in the
first place? From the comments, it seems to that for security/stability
reasons, and another reason is to make plugins get loaded from the build dir.

What about solely relying on envvars? Then there can be a shell-script if you
like the wrapper provided by libtool:

#!/bin/bash
# tools/run.sh -...

Re: [Wireshark-commits] master 43a81b6: Add some information on running from the build directory. Joerg Mayer (Jul 31)
I hope to look into this soon ('ish)

Ciao
Jörg

Re: [Wireshark-commits] master 43a81b6: Add some information on running from the build directory. Joerg Mayer (Jul 31)
If I understand cmake correctly - and that's a big if - it will build the code
to be run from the build environment. Make install will relink the code to
run from the install environment.

Ciao
Jörg

Wireshark 1.10.9 is now available Wireshark announcements (Jul 31)
I'm proud to announce the release of Wireshark 1.10.9.

__________________________________________________________

What is Wireshark?

Wireshark is the world's most popular network protocol
analyzer. It is used for troubleshooting, analysis, development
and education.
__________________________________________________________

What's New

Bug Fixes

The following vulnerabilities have been fixed.
*...

More Lists

Dozens of other network security lists are archived at SecLists.Org.


[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]