Wireshark-announce: [Wireshark-announce] Wireshark 1.0.2 is now available
: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx
: Thu, 10 Jul 2008 14:15:35 -0700
-----BEGIN PGP SIGNED MESSAGE-----
I'm proud to announce the release of Wireshark 1.0.2.
What is Wireshark?
Wireshark is the world's most popular network protocol analyzer.
It is used for troubleshooting, analysis, development, and
The following vulnerabilities have been fixed. See the security
advisory for details and a workaround.
o Wireshark could crash while reassembling packets.
Versions affected: 0.8.19 to 1.0.1
The following bugs have been fixed:
o Dumpcap could crash on some versions of Windows (primarily
Vista). (Bug 2677)
New and Updated Features
There are no new or updated features in this release.
New Protocol Support
There are no new protocols in this release.
Updated Protocol Support
There are no updated protocols in this release.
New and Updated Capture File Support
There is no new or updated capture file support in this release.
Wireshark source code and installation packages are available from
the download page on the main web site.
Most Linux and Unix vendors supply their own Wireshark packages.
You can usually install or upgrade Wireshark using the package
management system specific to that platform. A list of third-party
packages can be found on the download page on the Wireshark web
Wireshark and TShark look in several different locations for
preference files, plugins, SNMP MIBS, and RADIUS dictionaries.
These locations vary from platform to platform. You can use
About->Folders to find the default locations on your system.
Wireshark may appear offscreen on multi-monitor Windows systems.
Wireshark might make your system disassociate from a wireless
network on OS X. (Bug 1315)
Dumpcap might not quit if Wireshark or TShark crashes. (Bug 1419)
Wireshark is unable to decrypt WPA group keys. (Bug 1420)
The BER dissector might infinitely loop. (Bug 1516)
Wireshark can't dynamically update the packet list. This means
that host name resolutions above a certain response time threshold
won't show up in the packet list. (Bug 1605)
Capture filters aren't applied when capturing from named pipes.
Wireshark might freeze when reading from a pipe. (Bug 2082)
Capturing from named pipes might be delayed on Windows. (Bug 2200)
Filtering tshark captures with display filters (-R) no longer
works. (Bug 2234)
Community support is available on the wireshark-users mailing
list. Subscription information and archives for all of Wireshark's
mailing lists can be found on the web site.
Commercial support and development services are available from
Frequently Asked Questions
A complete FAQ is available on the Wireshark web site.
wireshark-1.0.2.tar.bz2: 13064896 bytes
wireshark-1.0.2.tar.gz: 16762866 bytes
wireshark-setup-1.0.2.exe: 22192304 bytes
wireshark-1.0.2.u3p: 20047161 bytes
WiresharkPortable-1.0.2.paf.exe: 17492451 bytes
Wireshark 1.0.2 Intel.dmg: 35834912 bytes
MD5(Wireshark 1.0.2 Intel.dmg)=0414ba5b77686caf93243de19e4964b7
SHA1(Wireshark 1.0.2 Intel.dmg)=a2c7dc95f2cb6ce26d4ab65f762417d8d82656a0
RIPEMD160(Wireshark 1.0.2 Intel.dmg)=28468edc93702f7b128625790918480af08a2375
patch-wireshark-1.0.1-to-1.0.2.diff.bz2: 18972 bytes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
-----END PGP SIGNATURE-----