|Main Archive Page > Month Archives > wireshark-dev archives|
-----BEGIN PGP SIGNED MESSAGE-----
Wireshark 1.0.16 is now available.
What is Wireshark?
Wireshark is the world's most popular network protocol analyzer.
It is used for troubleshooting, analysis, development, and
The following vulnerability has been fixed. See the security
advisory for details and a workaround.
o Wireshark is vulnerable to DLL hijacking as described in
Microsoft Security Advisory 2269637. This problem is fully
fixed on Windows XP SP1 and later. It is partially fixed on
Windows 2000 and XP without service packs. We expect to
address those platforms in future releases. If you are running
Wireshark on Windows 2000 or XP we recommend that you only
open capture files within Wireshark. (Bug 5133)
Versions affected: All previous Windows versions up to and
including 1.0.15 and 1.2.10.
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.
Wireshark source code and installation packages are available from
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)
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.16.tar.bz2: 13448096 bytes
wireshark-1.0.16.tar.gz: 17219618 bytes
wireshark-setup-1.0.16.exe: 22468135 bytes
wireshark-1.0.16.u3p: 20186713 bytes
WiresharkPortable-1.0.16.paf.exe: 17602232 bytes
Wireshark 1.0.16 Intel.dmg: 37254326 bytes
MD5(Wireshark 1.0.16 Intel.dmg)=f66f202dfe6f70738913f151790108bd
SHA1(Wireshark 1.0.16 Intel.dmg)=970c0913751d580492a77d3c50340428ec50e8da
Wireshark 1.0.16 PPC.dmg: 39139661 bytes
MD5(Wireshark 1.0.16 PPC.dmg)=a61ab7f5224f85b2567dc06bd4f72c04
SHA1(Wireshark 1.0.16 PPC.dmg)=169785b6af7331fd641a6d91b670e2088c4116a0
RIPEMD160(Wireshark 1.0.16 PPC.dmg)=f0b1f74298ed43f802b450d5a1f17419091fb97b
patch-wireshark-1.0.15-to-1.0.16.diff.bz2: 43540 bytes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
Sent via: Wireshark-dev mailing list <email@example.com>