[Wireshark-dev] Restarting WinPcap development

As you may have noticed, the WinPcap project has been dormant for some time. In order to help the project move forward I've been working with Gianluca to convert the private WinPcap CVS repository to a public Gerrit project at https://code.wireshark.org/review. Additionally Riverbed has agreed to o

Re: [Wireshark-dev] Qt version for the Wireshark Windows build

It looks like direct downloads are available at https://download.qt.io/official_releases/qt/ I got there by copying one of the online installer links listed at https://www.qt.io/download-open-source/ and trimming off the file and version. On 6/3/15 7:32 AM, Roland Knall wrote: > Hi > > Is i

Re: [Wireshark-dev] Qt version for the Wireshark Windows build

Qt are available in the archive > -> http://download.qt.io/archive/qt/ and so on, but wondered if that > was the version that he said actually downloaded a 32 bit copy. > > > On 3 June 2015 at 16:39, Gerald Combs <mailto:ger...@wireshark.org>&

[Wireshark-dev] Buildbot outage

Most of our builders are currently unavailable due to a network outage. I don't have an ETA on a fix but our provider is working on the issue. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/

[Wireshark-dev] PVS-Studio analysis of Wireshark

Andrey Kalashnikov analyzed Wireshark using the PVS-Studio static analyzer and wrote up an interesting report at http://www.viva64.com/en/b/0328/ . It looks like we've fixed a couple of the errors independently but the rest look easy enough to fix. _

[Wireshark-dev] Planning the next major release

We often make major releases in June, just before Sharkfest. That probably won't happen this year. A major release now would mean either releasing 2.0 (featuring the Qt UI) without feature parity with the GTK+ UI, or releasing 1.14 (featuring the GTK+ UI). I'm not particularly fond of either choice

Re: [Wireshark-dev] Code Contribution

Short answer: Go to https://code.wireshark.org/review/login/ and log in using your Google, GitHub, or an OpenID account. The long answer involves OpenID, OAuth, a group in very large company deprecating one of its authentication services, a different group in *that same very large company* refusin

Re: [Wireshark-dev] hope to support NPcap by improving WinPcap's DLL searching logic

On 6/10/15 7:43 AM, Alexis La Goutte wrote: > > > On Wed, Jun 10, 2015 at 4:34 PM, Pascal Quantin > wrote: > > 2015-06-05 19:24 GMT+02:00 Yang Luo >: > > Hi list, > > I'm developing NPcap, an alternative to or

[Wireshark-dev] Wireshark 1.12.6 is now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.12.6. __ What is Wireshark? Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting,

[Wireshark-dev] Wireshark 1.99.7 is now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.99.7. This is an experimental release intended to test new features for Wireshark 2.0. __ What is Wireshark? Wireshark is

Re: [Wireshark-dev] Automated build for 1.99.8 on Windows missing?

On 6/29/15 5:51 AM, Roland Knall wrote: > Hi > > I was just trying to find an automated build for Windows > on https://www.wireshark.org/download/automated/ . The only builds I can > find are for 1.12rc7 and PDB builds for 1.99.8, but no builds for 1.99.8 in > either x86 or x64 directories. > >

Re: [Wireshark-dev] Automated build for 1.99.8 on Windows missing?

On 6/29/15 10:57 AM, Graham Bloice wrote: > On 29 June 2015 at 16:54, Gerald Combs <mailto:ger...@wireshark.org>> wrote: > > On 6/29/15 5:51 AM, Roland Knall wrote: > > Hi > > > > I was just trying to find an automated build for Windows

Re: [Wireshark-dev] odd Windows petri-dish failure

On 7/8/15 1:46 PM, Hadriel Kaplan wrote: > Anyone seen this type of petri-dish failure before, on the Windows > petri-dish, and know what it means? > > Resolving deltas: 71% (3551/4999) > Resolving deltas: 72% (3600/4999) > error: index-pack died of signal 11 > fatal: index-pack failed >

Re: [Wireshark-dev] Windows driver signing certificate purchase decision for WinPcap and Npcap

On 7/21/15 3:40 AM, Graham Bloice wrote: > > > On 21 July 2015 at 11:25, Pascal Quantin > wrote: > > > Le 21 juil. 2015 11:38 AM, "Graham Bloice" > a écrit : > > > > > > > > On 21 July 2015 at 07:06,

[Wireshark-dev] Wireshark 1.99.8 is now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.99.8. This is a semi-experimental release intended to test new features for Wireshark 2.0. __ What is Wireshark? Wireshar

[Wireshark-dev] We now have an EV code signing certificate!

Our (the Wireshark Foundation's) EV code signing certificate + token arrived today. I have successfully configured the token and used it to sign an executable. ___ Sent via:Wireshark-dev mailing list Archives:https://w

Re: [Wireshark-dev] We now have an EV code signing certificate!

On 7/24/15 4:47 PM, Graham Bloice wrote: > On 24 July 2015 at 21:24, Gerald Combs <mailto:ger...@wireshark.org>> wrote: > > Our (the Wireshark Foundation's) EV code signing certificate + token > arrived today. I have successfully configured the token and u

Re: [Wireshark-dev] unicode replacement character in online docs

On 8/5/15 6:57 AM, Evan Huus wrote: > On Wed, Aug 5, 2015 at 9:49 AM, Hadriel Kaplan > wrote: >> Anyone else seeing the unicode replacement character all over the >> online auto-generated docs? (user guide and developer guide) > > Yup, and that's new AFAIK. Anybody know if something's change on t

Re: [Wireshark-dev] Microsoft Visual C Version 6support isa bitoutdated ...

This should be fixed in r20397. Douglas Pratley wrote: > Looks like this is related to revision 20388 - changing decryption keys > to use GByteArray rather than GString for SSID in > epan\crypt\airpdcap_user.h. Not sure why it only affects Windows. > Nothing to do with MSVC version (as stated alre

Re: [Wireshark-dev] [The Wireshark Wiki] Update of "FrontPage" by nickvlas

Ulf Lamping wrote: > Wireshark Wiki - Do not reply wrote: >> Dear Wiki user, >> >> You have subscribed to a wiki page or wiki category on "The Wireshark Wiki" >> for change notification. >> >> The following page has been changed by nickvlas: >> http://wiki.wireshark.org/FrontPage >> >> ---

Re: [Wireshark-dev] Increasing buildbot trigger delay

Jaap Keuter wrote: > Hi Gerald, > > I've noticed a trend in which commits are grouped together within a short > timespan, eg. people committing a change in multiple steps. Currently the > buildbot takes a one minute delay before starting a build. This is usually > too short resulting in a two cons

Re: [Wireshark-dev] [Wireshark-bugs] [Bug 1287] Problem with capturing on an Accton EN1207D ethernet card

Ulf Lamping wrote: > the "built docs" as the last step. Obviously, the docs must be generated > at least before the "created package" step (maybe even before the > compiling step). Gerald, could you please change this sequence in the > Win32 buildbot? Then we can simply enable the setting in con

Re: [Wireshark-dev] [Wireshark-commits] rev 20385: /trunk/ /trunk/packaging/nsis/: wireshark.nsi /trunk/: Makefile.am

Ulf Lamping wrote: > [EMAIL PROTECTED] wrote: >> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=20385 >> >> User: lego >> Date: 2007/01/10 09:48 PM >> >> Log: >> Add the example_snmp_users_file to the ditribution >> >> Directory: /trunk/packaging/nsis/ >> ChangesPath

Re: [Wireshark-dev] Add U3 package to the release process?

Graeme Lunt wrote: > On 1/10/07, Gerald Combs <[EMAIL PROTECTED]> wrote: >> I just modified the U3 package build to add the version number to the >> package file name. (Hopefully this doesn't break anything Graeme is doing). > > Shouldn't break anything. >

Re: [Wireshark-dev] airpdcap.c with gtk1.2 does not compile anymore

This should be fixed in r20438. Sebastien Tandel wrote: > Hi, > > >in rev20388 some functions have been defined in strutil.c (only for > gtk >= 2). > These functions are used by airpdcap.c/airpcap_loader.c in code for any > version of gtk. > > epan/.libs/libwireshark.so: undefined reference

Re: [Wireshark-dev] Add U3 package to the release process?

Graeme Lunt wrote: > Gerald, > >> It's now part of the build process. Buildbot-generated U3 packages are >> now deposited in http://www.wireshark.org/download/automated/win32/, >> just like the executable installers. > > Thanks. > > If I write something that verifies the integrity of the genera

Re: [Wireshark-dev] Add U3 package to the release process?

Graeme Lunt wrote: > Gerald, > >> It's now part of the build process. Buildbot-generated U3 packages are >> now deposited in http://www.wireshark.org/download/automated/win32/, >> just like the executable installers. > > Thanks. > > If I write something that verifies the integrity of the genera

Re: [Wireshark-dev] [Wireshark-commits] rev 20465: /trunk-0.99.5/

I've created a branch for 0.99.5, and will start working on a prerelease. If any commits need to be copied from /trunk to /trunk-0.99.5, please add them to the 0.99.5 pending section at http://wiki.wireshark.org/Development/Roadmap. [EMAIL PROTECTED] wrote: > http://anonsvn.wireshark.org/viewvc/v

Re: [Wireshark-dev] [Patch] packet-kerberos.c

Gisle Vanem wrote: > "Sebastien Tandel" <[EMAIL PROTECTED]> wrote: > >>> PS. What's up with the mailing-list software? Every message looks >>> like> crap; all line-endings are missing. Is the ML-software running >>> on a Mac?> Everything's fine here ... maybe a new feature of >>> Outlook Express

Re: [Wireshark-dev] Buildbot builds don't show up for download

I updated Cygwin on the Windows builder a few days ago. It looks like that exposed a bug in make-version.pl which kept the revision number from being appended to the package names. Revision-less packages don't get copied to the web site automatically (otherwise we might end up with several wiresh

[Wireshark-dev] Wireshark 0.99.5pre1 is now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wireshark 0.99.5pre1 is now available for testing. Source code and a Windows installer can be downloaded immediately from http://www.wireshark.org/download/prerelease/wireshark-0.99.5pre1.tar.gz http://www.wireshark.org/download/prerelease/wireshark-

Re: [Wireshark-dev] How do I initialise a boolean preference

You might try checking Help->About Wireshark->Folders. Specific locations vary by platform and compile-time options. Hal Lander wrote: > I did not realise there was a preference file. > > Now looking at http://www.wireshark.org/docs/man-pages/tshark.html I can > see there should be a global and

Re: [Wireshark-dev] Time to bump version number in svn?

Done (the places are in configure.in and config.nmake). Jaap Keuter wrote: > Hi, > > I guess so, but there's a number of places where that needs to be changed. > I think Gerald has them summed up on his release checklist (?). > > Thanx, > Jaap > > On Sat, 20 Jan 2007, Stephen Fisher wrote: > >

Re: [Wireshark-dev] [Patch] airpcap_loader.h

Checked in with r20535. Thanks! Gisle Vanem wrote: > A case of conflict in definition and implementation: > > --- SVN-Latest\airpcap_loader.h Mon Jan 22 22:20:27 2007 > +++ airpcap_loader.hMon Jan 22 22:37:08 2007 > @@ -309,7 +309,7 @@ > * Will return null if no device is found. > */ > GL

[Wireshark-dev] Include WinPcap 4.0 with the next release?

WinPcap 4.0 final is due out in a few days. It adds support for Vista, is synced with libpcap 0.9.5, and has many other fixes and updates. Would it make sense to ship it with the 0.99.5 release instead of WinPcap 3.1? ___ Wireshark-dev mailing list Wires

Re: [Wireshark-dev] [Wireshark-commits] rev 20546: /trunk/epan/dissectors/ /trunk/epan/dissectors/: packet-ieee80211.c

Joerg Mayer wrote: > Gerald, > > On Wed, Jan 24, 2007 at 07:22:15PM +, [EMAIL PROTECTED] wrote: >> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=20546 >> >> Directory: /trunk/epan/dissectors/ >> ChangesPath Action >> +104 -104 packet-ieee80211.c

[Wireshark-dev] 802.11 whdrs array needed?

The 802.11 dissector has the following code: wlan_hdr *volatile whdr; static wlan_hdr whdrs[4]; whdr= &whdrs[0]; It looks like whdrs[1] through whdrs[3] are never used. Should the code be modified to rotate through each member of whdrs, similar to the fmtbuf arrays in strutil.c? _

Re: [Wireshark-dev] address_to_str_buf not checking available buffer length

Andrej Mikus wrote: > In file to_str.c I notice function address_to_str_buf that takes buf_len > as argument, but does not use it for IPv4 and IPv6 addresses: > > void > address_to_str_buf(const address *addr, gchar *buf, int buf_len) > { > switch(addr->type){ > case AT_IPv4: > ip_to_str_

Re: [Wireshark-dev] [Wireshark-users] [ANNOUNCE] WinPcap 4.0 has been released

Whoah there! :) I just copied WinPcap 4.0 into the 0.99.5 trunk, and plan on releasing 0.99.5pre2 later today. I'll send a message when it's ready. I'm hoping to have 0.99.5 final out on Thursday or Friday. Jaap Keuter wrote: > Hi List, > > On the back of WinPCap 4.0 our fearless leader has

Re: [Wireshark-dev] wireshark-setup-0.99.5pre2-20620.exe large icon missing

Jaap Keuter wrote: > Hi list, > > When downloading the Win32 installer on WinXP SP2 and looking at the > properties of it, there's no icon. I see that the icon used if the > bevelled one, I don't know what the firefox download window and the > properties tab uses. Can you check the properties for

Re: [Wireshark-dev] [Wireshark-commits] rev 20608: /trunk/gtk/ /trunk/gtk/: sctp_assoc_analyse.c sctp_stat.c sctp_stat.h sctp_stat_dlg.c

Done. Michael Tuexen wrote: > Gerald, > > could you please copy this over to 0.99.5 tree? These are bugfixes which > improves the handling of some SCTP trace captured in real life > traces. > > Best regards > Michael > On Jan 29, 2007, at 8:45 PM, [EMAIL PROTECTED] wrote: > >> http://anonsvn.wi

Re: [Wireshark-dev] What about a universal XML parsing dissector

John R. wrote: > NetPDL or things like it are the way to do this. However, it is not > realistic to think that you will never need to have hooks in the XML > descriptors for custom code. For example, say Protocol X uses some > funny encoding for a field that no one else uses (beyond just shifts >

[Wireshark-dev] Wireshark 0.99.5pre2 is now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wireshark 0.99.5pre2 is now available for testing. Source code and a Windows installer can be downloaded immediately from http://www.wireshark.org/download/prerelease/wireshark-0.99.5pre2.tar.gz http://www.wireshark.org/download/prerelease/wireshark-

Re: [Wireshark-dev] [patch] address_to_str_buf not checking available buffer length

07 12:29:30 +0100, Andrej Mikus wrote: >> On Mon, 29.Jan.07 12:49:00 -0800, Gerald Combs wrote: >>> Andrej Mikus wrote: >>> >>>> In file to_str.c I notice function address_to_str_buf that takes buf_len >>>> as argument, but does not use it for IPv4 and IPv6

Re: [Wireshark-dev] Win32 buildbot should switch over to use Makefile.nmake

Ulf Lamping wrote: > Hi! > > The Win32 buildbot currently fails to generate the docbook docs. This is > due to problems with generating the svn_version.xml, and that is due to > the known bash CR/NL problems. > > Instead of trying to fix this, the buildbot should use the new > Makefile.nmake (

Re: [Wireshark-dev] Display Filter References

Graeme Lunt wrote: > When/how do the display filter pages get updated? > Some of the new protocols (e.g. DMP, PKCS12) do not have corresponding > pages. They get updated as a part of the release process, so that version information can be added. ___ Wire

[Wireshark-dev] Wireshark 0.99.5 is now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wireshark 0.99.5 has been released. 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 vulnerab

Re: [Wireshark-dev] U3 questions/remarks

Guy Harris wrote: > Graeme Lunt wrote: > >> Well, I've just had a quick look at this and it appears to be because the >> Wireshark icon I put into the manifest has more than 256 colours. This is >> not a problem for the main launchpad window but it apparently a problem for >> the "More Programs" s

[Wireshark-dev] Add BPF filtering to Wiretap?

Would it make sense to add BPF filtering to Wiretap via pcap_offline_filter()? This would let you pre-filter capture files in Wireshark and TShark (and possibly editcap) without having to build a protocol tree. The main disadvantage is that it's only available in WinPcap.

Re: [Wireshark-dev] Patch - Decode for 802.11n Beacon/Probe/Association Information Elements

Clay Jones wrote: > This patch adds decodes for 802.11n information elements. Since 802.11n > isn't a formal standard yet they are not using the final packet > structures or ie type numbers. But there are already 802.11n pre > release devices out there and these decodes do seem to correctly decod

Re: [Wireshark-dev] Controlling Tshark output format

Would it make more sense to extend the current -T flag e.g. -Tfields,ip,udp,tcp.srcport instead? This would tie the output spec directly to the "fields" format. It might be useful to be able to restrict the fields in the "pdml", "ps", and "text" formats as well. Ian Schorr wrote: > This woul

[Wireshark-dev] Windows named pipe support

I just enabled code in capture_loop.c which allows capturing from named pipes under Windows, e.g. "tshark -i \\.\pipe\capture" Can someone else test the change and verify that it works on their system? ___ Wireshark-dev mailing list Wireshark-dev@wiresha

Re: [Wireshark-dev] Win32 buildbot unhappy while building docs

It looks like the builder hung at some point. I've restarted it. Douglas Pratley wrote: > For what it's worth, "wsug.validated" builds fine on my machine, both > using nmake and cygwin make. > > Unless I've not noticed a commit that fixes this, perhaps this is a > problem with the build machine

Re: [Wireshark-dev] The Win32 buildbot is still very unhappy ...

Ulf Lamping wrote: > Hi Gerald! > > Looking at the logs, I don't have a clue what the problem is. > > Any ideas to solve it? Rebooting seems to have worked. :) ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/

Re: [Wireshark-dev] I've "officially" dropped support for Windows NT 4.0 ...

Michael Zuffoletti wrote: > I didn't have a problem installing the official 0.99.5 build with > WinPcap 4 on NT4. I didn't notice any warning or install failure. > However, this install as well as my own build of trunk rev 20835 with > MSVC6 would not run. They gave the "PrintDlgExW could not be lo

Re: [Wireshark-dev] crypt-sha1

The wiki page has been updated. Maybe we should have a svn diff | gzip | send-the-patch-to-bugzilla pipeline. :) Sebastien Tandel wrote: > I've never said there was a lot of changes ;) > > Concerning the compressed patches, I will keep in mind for the next time. > However, if you want to

Re: [Wireshark-dev] Buildbot compile flags

Joerg Mayer wrote: > On Thu, Mar 22, 2007 at 08:01:50PM -0700, Stephen Fisher wrote: >> On Thu, Mar 22, 2007 at 07:47:35PM -0700, Guy Harris wrote: >> The alternative is to compile with -std=c99 for the long long case, but >> do we really want to do that? I agree that -pedantic is a bit too much

Re: [Wireshark-dev] Broken Record - Release tag

Bryant Eastham wrote: > Gerald Combs wrote: > >> /trunk-0.99.2 was copied from /trunk last week. Once the 0.99.2 release > >> is made it will be moved to /releases/wireshark-0.99.2. Some time in > >> the future we'll start over again by copying /trunk to

[Wireshark-dev] Update official Windows build?

The official Windows installers are still built using Visual Studio 6.0. I'd like to switch over to Visual C++ 2005 Express Edition before the next release. Is there any reason not to do this? ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org h

Re: [Wireshark-dev] Update official Windows build?

ere are better solutions than MSI Installer: > NSIS: http://nsis.sourceforge.net/Main_Page > Bitrock installer: > http://bitrock.com/products_installbuilder_overview.html (Platform > independent installer) > > > Gerald Combs schrieb: >> The official Windows installers ar

Re: [Wireshark-dev] The "war against warnings" - mission accomplished!

Richard van der Hoff wrote: > Stephen Fisher wrote: >> On Tue, Apr 03, 2007 at 03:11:38PM +0100, Richard van der Hoff wrote: >> >>> I guess I'm not quite up to speed with the state of this project... Am >>> I right in thinking that warnings have only been purged successfully >>> so far for the wi

[Wireshark-dev] Changes to make-dissector-reg.py

In order to speed up compile time, I've added a cache to make-dissector-reg.py (the script used to generate register.c). When you update a dissector and recompile, it _should_ pull the registration data for unchanged dissectors from its cache, thereby speeding up compilation time. On my home mach

Re: [Wireshark-dev] [PATCH] Adding option to IEEE 802.11 to ignore wep bit with IV

Checked in. Thanks! Stig Bjørlykke wrote: > Hi. > > This patch adds an option to IEEE 802.11 to ignore the wep bit with IV, > as mentioned in > http://www.wireshark.org/lists/wireshark-dev/200704/msg00021.html > > I also fixed a bug where the packet is dissected different in the Packet > List w

Re: [Wireshark-dev] windows buildbot problem

Richard van der Hoff wrote: > I need your help to fix a problem with the Windows buildbot. > > A while ago I made it run the unit tests in the epan directory as part > of the testing phase. This works fine under Linux, but on windows, the > test programs don't seem to want to run. They don't giv

Re: [Wireshark-dev] Bug in register.c generation

Joerg Mayer wrote: > Hello, > > I've got a problem with the generation of the register.c file: > > [EMAIL PROTECTED]:~/work/wireshark/trunk/epan/dissectors> sort register.c | > uniq -c | grep -v " 1 " > 2 > 2 { > 2 } > 2 {extern void proto_register_cisco_oui (void); >

Re: [Wireshark-dev] lex on ubuntu buildbot

Sebastien Tandel wrote: > Hi, > > >does anyone know what's the lexer (and version) used on the ubuntu > buildbot machine? Lex says: $ lex --version lex 2.5.33 ___ Wireshark-dev mailing list [EMAIL PROTECTED] http://www.wireshark.org/mailman/listin

Re: [Wireshark-dev] [PATCH] Fix for 802.11 WMM TSPEC dissector

Tuomas Maattanen wrote: > TS Info field should be three bytes long, not two. > Suspension Interval field is missing altogether, shifting all other > fields by four bytes. > Maximum Burst Size, Minimum PHY Rate, Peak Data Rate and Delay Bound are > in wrong order. > > I have attached a patch that f

[Wireshark-dev] OS X builder down

The OS X builder (an aging Power Mac G4) went down early this morning and now refuses to boot. I haven't had time to look at the problem in detail, but we may be without fuzz testing for a while. ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org

Re: [Wireshark-dev] no more Python 2.1.1

Jeff Morriss wrote: > My Solaris builds now fail with: > >> Making register.c with python >> Traceback (most recent call last): >> File "../../tools/make-dissector-reg.py", line 98, in ? >> cur_mtime = os.fstat(file.fileno()).st_mtime >> AttributeError: 'tuple' object has no attribute 'st_mt

Re: [Wireshark-dev] [PATCH] Fix break placement for control frame in packet-ieee80211.c

Checked in. Thanks! Stig Bjørlykke wrote: > Hi. > > Fix break placement for control frames in dissect_ieee80211_common() > > > > > > > ___ > Wireshark-dev mailing list > Wire

Re: [Wireshark-dev] OpcUa update

Gerhard Gappmeier wrote: > Hi, > >> A fuzzed Sample.cap file (attached) crashed TShark and took a *very* >> long time (2 mins) to load in WS. >> > it loads the file imediately on my computer without any delay. > I tried the fuzzy file also with tshark. > I called "tshark -r sample.cap", is this ri

Re: [Wireshark-dev] Win32 buildslave failure

Bill Meier wrote: > My belief is that this is not a bug in GTK/GDK but rather an attempt by > wireshark to output an error message (pop up window ?) during one of the unit > tests. Wireshark is being run from a shell command line for the unit tests > and maybe this test setup doesn't quite work

Re: [Wireshark-dev] Win32 buildslave failure

Bill Meier wrote: > What's also interesting is that the last build took much less time than the > previous builds. (The compile step took just 30 mins or so instead of > hours!). > > Are there other things running on that node or is this a case of "Windows > strikes again !!" :) It's a VM shar

Re: [Wireshark-dev] GTK 2.10.12

The gimp.org page hasn't been updated yet, but updated binaries are available at http://ftp.gnome.org/pub/GNOME/binaries/win32/ . I've updated the wireshark-win32-libs repository, so you'll need to run 'nmake -f makefile.nmake setup' if you've updated SVN recently. Anders Broman wrote: > Hi, > We

Re: [Wireshark-dev] Improve wireshark to fault injection tool

[EMAIL PROTECTED] wrote: > Hello everybody, > > I need to improve wireshark to a fault injection tool. > > It's a fault communication injector that i need to create from the wireshark > source. > > To do this, i want to use the libnet librairie in order to make fault like : > - delay time fault

[Wireshark-dev] Update to the COPYING file

Back in October there was a discussion about the fact that we have a "click-through" agreement in the Windows installer requiring that users accept the GPL. After reading through the thread again, I've updated the summary in the COPYING file to read: Wireshark is distributed under the G

Re: [Wireshark-dev] Please test fix Critical bug 1360

Jaap Keuter wrote: > Hi list, > > Can someone test the current Windows build against the capture in bug > 1360? It's a critical bug we need to get closed, like the other 13 > criticals. It appears to be fixed, so I closed the bug. > Since we've almost 200 bugs open, 14 critical, we need to get c

Re: [Wireshark-dev] Update to the COPYING file

Ulf Lamping wrote: > Gerald Combs wrote: >> Back in October there was a discussion about the fact that we have a >> "click-through" agreement in the Windows installer requiring that users >> accept the GPL. After reading through the thread again, I've updated

Re: [Wireshark-dev] PAD file and automatic version checking

Jaap Keuter wrote: > Hi Gerald, > > On the Wireshark download page a PAD file can be found that can be used > for version checking. Version checking is an item on the release list for > .6 (Win32). What I can't figure out is how the update is being checked on > the client PC? How/by what software

Re: [Wireshark-dev] [Wireshark-commits] rev 21831: /trunk/ /trunk/epan/dissectors/: Makefile.nmake packet-ieee80211.c packet-ieee80211.h packet-radiotap.c /trunk/gtk/: Makefile.nmake airpcap_dlg.c air

We're working on a fix. Sorry for any inconvenience. Stephen Fisher wrote: > I'm getting compilation errors on a Windows box with AirPcap installed > since I did an svn update. I assume it's related to the check-in at the > bottom of this e-mail. The errors start with: > > C:\wireshark\airpc

Re: [Wireshark-dev] Wireshark and Microsoft Vista

Joerg Mayer wrote: > On Mon, May 21, 2007 at 08:17:40PM +0200, Ulf Lamping wrote: >>> Does Wireshark run on 32-bit Microsoft Vista? How about 64-bit >>> Microsoft Vista? If not, what are the plans to port Wireshark to Vista? >>> >> See http://www.wireshark.org/docs/wsug_html_chunked/ChIntroPlatf

Re: [Wireshark-dev] [Wireshark-commits] rev 21883: /trunk/ /trunk/: configure.in

Joerg Mayer wrote: > On Tue, May 22, 2007 at 07:52:14AM +, [EMAIL PROTECTED] wrote: >> People who want to build TShark for machines that don't have GTK+ >> installed, but don't want to build Wireshark because they can't install >> GTK+ on the build/target machine, can still do that; they jus

[Wireshark-dev] OS X builder

Thanks to Michael Tuexen, we once again have a working OS X builder (and this one's a lot faster). Fuzz testing is currently disabled, but we may be able to get it up and running soon. ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www

[Wireshark-dev] Next release (0.99.6)?

It's been a while since the last release, and we've accumulated a lot of bug fixes (some of which keep getting reported on Bugzilla). Once we get fuzz testing up and running again (and it's green for a few consecutive runs) I'd like to push out a new release. __

Re: [Wireshark-dev] WiMAX and M2M plugin code

It's strongly recommended, and has been discussed as a prerequisite in the past. If you're interested, you can run the fuzz tests yourself: http://wiki.wireshark.org/FuzzTesting Harvey, Michael wrote: > Sorry for the delay, I'm trying to get a capture released to you. Is > this a prerequisite for

Re: [Wireshark-dev] Automatically setting focus for display filter control no longer works [Patch]

The problem with only checking against GDK_CONTROL_MASK and GDK_MOD1_MASK (a.k.a. "Alt") is that we miss all the other strange and funky modifier keys that we might encounter. On a Mac here, holding down the command key generates an event->state value of 0x1010 (GDK_MOD2_MASK | GDK_META_MASK).

Re: [Wireshark-dev] WiMAX and M2M plugin code

; -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Gerald Combs > Sent: Thursday, May 24, 2007 10:57 AM > To: Developer support list for Wireshark > Subject: Re: [Wireshark-dev] WiMAX and M2M plugin code > > It's strongly recomme

Re: [Wireshark-dev] AirPDcap vs. AirPcap?

Stephen Fisher wrote: > I know what AirPcap is, but what is AirPDcap in the Wireshark code? Are > they related in some way? The AirPcap code is for 802.11 capture, and the AirPDcap code is for 802.11 decryption (WEP, WPA, and WPA2). They both touch the 802.11 dissector and the wireless toolbar,

Re: [Wireshark-dev] [Wireshark-commits] rev 22071: /trunk/ /trunk/doc/: dumpcap.pod /trunk/gtk/: capture_dlg.c capture_if_dlg.c capture_prefs.c

Bill Meier wrote: >> Add a capture_interface_list(), which works similar to >> get_interface_list() except that it forks dumpcap instead of calling >> the pcap routines directly. Use it in the GUI. >> >> Add a "-I" flag to dumpcap, which prints out verbose interface >> information. >> >>

Re: [Wireshark-dev] Next release (0.99.6)?

Buildbot has been (mostly) green for a while, and private fuzz tests haven't turned up any problems, so I'm going to create the 0.99.6 branch in the next couple of days. Please don't check in anything experimental until then. :) Gerald Combs wrote: > It's been a while

Re: [Wireshark-dev] Using pipes on Windows

[EMAIL PROTECTED] wrote: > Hi everyone. > > I am currently working with Wireshark 0.99.5. > > I know that it is possible on Unix machines to let Wireshark read from a > pipe. I am not really sure if it is possible on Windows. > > For this reason I tried the following (of course I wrote a bit so

Re: [Wireshark-dev] [Wireshark-commits] rev 22094: /trunk/ /trunk/epan/dissectors/: Makefile.common packet-frame.c packet-frame.h packet-ppi.c /trunk/wiretap/: libpcap.c wtap.c wtap.h

Stephen Fisher wrote: > Gerald, > > The check-in below broke the Unix builds with a few warnings treated as > errors. A few are simple fixes, but the inclusion of a wiretap header > in non-wiretap dissector code is getting a bit tricky. The compiler's > complaints are: > > cc1: warnings bein

[Wireshark-dev] [Fwd: [Wireshark-commits] rev 22110: /trunk-0.99.6/]

The 0.99.6 trunk has been created. I plan on releasing 0.99.6pre1 some time late next week, followed by 0.99.6 the week after (around the 28th). If any checkins need to be copied from /trunk to /trunk-0.99.6, please add them to the 0.99.6 pending list at http://wiki.wireshark.org/Development/Road

Re: [Wireshark-dev] (pre-)release buildbots?

It's at http://buildbot.wireshark.org/release/ . There are only two builders active (Windows and Linux). They're the same machines as the /trunk buildbot. Stephen Fisher wrote: > Gerald, > > Are the (pre-)releases built on the same buildbots as the SVN? Is there > another link to see the (pre

[Wireshark-dev] Wireshark 0.99.6pre1 is now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wireshark 0.99.6pre1 is now available for testing. Source code and a Windows installer can be downloaded immediately from http://www.wireshark.org/download/prerelease/wireshark-0.99.6pre1.tar.gz http://www.wireshark.org/download/prerelease/wireshark-

Re: [Wireshark-dev] Some minor issues with the 0.99.6pre1 release notes

Ulf Lamping wrote: > Duplicate entry: > > o Wireshark now supports display filter macros > > o [8]Display filter macros are now supported. > > Missing entries in > > New Protocol Support > > Updated Protocol Support > > New and Updated Capture File Support These have bot

[Wireshark-dev] 0.99.6 release postponed

A bug was recently discovered in WinPcap which can cause a system crash. WinPcap 4.0.1 will be released early next week, which will fix the bug. I'd like to hold off on releasing 0.99.6 so that we can include WinPcap 4.0.1 with the Wireshark installer. In the meantime I'll release 0.99.6pre2 tom

[Wireshark-dev] Wireshark 0.99.6pre2 is now available

Wireshark 0.99.6pre2 is now available for testing. Source code and a Windows installer can be downloaded immediately from http://www.wireshark.org/download/prerelease/wireshark-0.99.6pre2.tar.gz http://www.wireshark.org/download/prerelease/wireshark-0.99.6pre2.u3p http://www.wireshark.org/downloa

[Wireshark-dev] Wireshark conference

This is entirely hypothetical, but if someone were to host a 3-day Wireshark conference, what sort of sessions would you be interested in? If enough developers attended, would there be interest in a hackathon? ___ Wireshark-dev mailing list Wireshark-dev

Re: [Wireshark-dev] 0.99.6 release postponed

Frederic Peters in, which I've got lined up in my working > copy. Tomorrow morning, when I'm fresh and sober, I'll review them one > last time before committing. > > Thanx, > Jaap > > > Gerald Combs wrote: >> A bug was recently discovered in WinPc

<    3   4   5   6   7   8   9   10   11   12   >