Wireshark-dev: [Wireshark-dev] Wireshark 1.0.12 is now available
From: Gerald Combs <[email protected]>
Date: Wed, 31 Mar 2010 16:43:27 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm proud to announce the release of Wireshark 1.0.12.

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 bugs have been fixed:

     o The encapsulation abbreviation "bluetooth-h4" is ambiguous.
       (Bug 4613)

  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 new or updated protocols.

  New and Updated Capture File Support

   There is no new or updated capture file support.

Getting Wireshark

   Wireshark source code and installation packages are available from
   http://www.wireshark.org/download.html.

  Vendor-supplied Packages

   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
   site.

File Locations

   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.

Known Problems

   Wireshark may appear offscreen on multi-monitor Windows systems.
   (Bug 553)

   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.
   (Bug 1814)

   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)

Getting Help

   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
   CACE Technologies.

Frequently Asked Questions

   A complete FAQ is available on the Wireshark web site.

Digests

wireshark-1.0.12.tar.bz2: 13439241 bytes
MD5(wireshark-1.0.12.tar.bz2)=f53030d1ab0dc29a97fe282e5eb23912
SHA1(wireshark-1.0.12.tar.bz2)=24ebdc7dd9bbcb57bab678acad7b165ac0f0a686
RIPEMD160(wireshark-1.0.12.tar.bz2)=e870f2b6ff6213deb5566c2adb809c056d1a2a5f

wireshark-1.0.12.tar.gz: 17161588 bytes
MD5(wireshark-1.0.12.tar.gz)=120c784d9e57601a31c146191f90765a
SHA1(wireshark-1.0.12.tar.gz)=9aff85c06f848bd55be58db292f32abe9ac93464
RIPEMD160(wireshark-1.0.12.tar.gz)=cbde0b69e2ee4716208a06765b1bbc727fd20000

wireshark-setup-1.0.12.exe: 22419262 bytes
MD5(wireshark-setup-1.0.12.exe)=5ff794f05a421afeb3562009b92f6553
SHA1(wireshark-setup-1.0.12.exe)=2f7e79dbecacbf87fd1e6e475a604ff87f140e39
RIPEMD160(wireshark-setup-1.0.12.exe)=7b74a40581e3c929c6fda8181606a841d8eeb3e4

wireshark-1.0.12.u3p: 20161662 bytes
MD5(wireshark-1.0.12.u3p)=bc874f7348d66f72e846ce49b5194a73
SHA1(wireshark-1.0.12.u3p)=470420364fb1f42e7fea25c4eaa21a627621a24d
RIPEMD160(wireshark-1.0.12.u3p)=9950f601707332ea2ecc3bb51fea0027f38d388f

WiresharkPortable-1.0.12.paf.exe: 17581151 bytes
MD5(WiresharkPortable-1.0.12.paf.exe)=ff2db5e3431cd41d72e4f28e9e7ca923
SHA1(WiresharkPortable-1.0.12.paf.exe)=547cc0f488c8a1615e8daa12638279183de75633
RIPEMD160(WiresharkPortable-1.0.12.paf.exe)=6aa509eca7d62043ac18f29b9772f61c432db2d6

Wireshark 1.0.12 Intel.dmg: 37200756 bytes
MD5(Wireshark 1.0.12 Intel.dmg)=409cd4c92c3b86fa9f4e1fc43af94cf0
SHA1(Wireshark 1.0.12 Intel.dmg)=4edf3f9c67ad030e492f1d91263289b3ff937db7
RIPEMD160(Wireshark 1.0.12
Intel.dmg)=9c4bea81c7eb1ec4309cfb1e9b22cb791a29d4fa

Wireshark 1.0.12 PPC.dmg: 39071983 bytes
MD5(Wireshark 1.0.12 PPC.dmg)=b0e60dfd514089601ddcf5e897cdbafd
SHA1(Wireshark 1.0.12 PPC.dmg)=be7f18b112bd19c7ed86d03f107a7086b9c7f30c
RIPEMD160(Wireshark 1.0.12 PPC.dmg)=e6cad240866881dfa1aaff37e028755356ee27c7

patch-wireshark-1.0.11-to-1.0.12.diff.bz2: 55943 bytes
MD5(patch-wireshark-1.0.11-to-1.0.12.diff.bz2)=2c1b8fef6e0b6eab2536edb2b3318adf
SHA1(patch-wireshark-1.0.11-to-1.0.12.diff.bz2)=e7cf168ae38cb3a0754c0676a1901f7739f680c3
RIPEMD160(patch-wireshark-1.0.11-to-1.0.12.diff.bz2)=54f2bab5f7d24ab24f030309c96da9336979f7fd

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuz3h8ACgkQpw8IXSHylJr/6gCeM0CMiwyw9m9jmIOjUE5TwWmO
90MAoNf4WfIuCjh1k6B3MYn5pE9R4p9L
=WQO4
-----END PGP SIGNATURE-----