Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: [Wireshark-dev] Wireshark 1.2.2 is now available

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 15 Sep 2009 13:47:41 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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

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. See the security
   advisory for details and a workaround.

     o The GSM A RR dissector could crash. (Bug 3893)

       Versions affected: 1.2.0 to 1.2.1

     o The OpcUa dissector could use excessive CPU and memory. (Bug
       3986)

       Versions affected: 0.99.6 to 1.0.8, 1.2.0 to 1.2.1

     o The TLS dissector could crash on some platforms. (Bug 4008)

       Versions affected: 1.2.0 to 1.2.1

   The following bugs have been fixed:

     o The "Capture->Interfaces" window can't be closed. (Bug 1740)

     o tshark-1.0.2 (dumpcap) signal abort core saved. (Bug 2767)

     o Memory leak fixes. (Bug 3330)

     o Display filter autocompletion doesn't work for some RADIUS and
       WiMAX ASNCP fields. (Bug 3538)

     o Wireshark Portable includes wrong WinPcap installer. (Bug
       3547)

     o Crash when loading a profile. (Bug 3640)

     o The proto,colinfo tap doesn't work if the INFO column isn't
       being printed. (Bug 3675)

     o Flow Graph adds too much unnecessary garbage. (Bug 3693)

     o The EAP Diameter dictionary file was missing in the
       distribution. (Bug 3761)

     o Graph analysis window is behind other window. (Bug 3773)

     o IKEv2 Cert Request payload dissection error. (Bug 3782)

     o DNS NAPTR RR (RFC 3403) replacement MUST be a fully qualified
       domain-name. (Bug 3792)

     o Malformed RTCP Packet error while sending Payload specific
       RTCP feedback packet( as per RFC 4585). (Bug 3800)

     o 802.11n Block Ack packet Bitmap field missing. (Bug 3806)

     o Wireshark doesn't decode WBXML/ActiveSync information
       correctly. (Bug 3811)

     o Malformed packet when IPv6 packet has Next Header == 59. (Bug
       3820)

     o Wireshark could crash while reading an ERF file. (Bug 3849)

     o Minor errors in gsm rr dissectors. (Bug 3889)

     o WPA Decryption Issues. (Bug 3890)

     o GSM A RR sys info dissection problem. (Bug 3901)

     o GSM A RR inverts MEAS-VALID values. (Bug 3915)

     o PDML output leaks ~300 bytes / packet. (Bug 3913)

     o Incorrect station identifier parsing in Kingfisher dissector.
       (Bug 3946)

     o DHCPv6, Vendor-Specific Informantion, SubOption"Option
       Request" parser incorrect. (Bug 3987)

     o Wireshark could leak memory while analyzing SSL.

     o Wireshark could crash while updating menu items after reading
       a file in some cases.

     o The Mac OS X ChmodBPF script now works correctly under Snow
       Leopard.

  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

   DCERPC, DHCPv6, DNS, E.212, GSM A RR, GTPv2, H.248, IEEE 802.11,
   IPMI, ISAKMP/IKE, ISUP, Kingfisher, LDAP, OpcUA, RTCP, SCTP, SIP,
   SSL, TCP, WBXML, ZRTP

  Updated Capture File Support

   ERF

Getting Wireshark

   Wireshark source code and installation packages are available from
   the download page on the main web site.

  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)

   Filtering tshark captures with display filters (-R) no longer
   works. (Bug 2234)

   The 64-bit Windows installer does not ship with the same libraries
   as the 32-bit installer.

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, training, and development services are
   available from CACE Technologies.

Frequently Asked Questions

   A complete FAQ is available on the Wireshark web site.


Digests

wireshark-1.2.2.tar.bz2: 15186702 bytes
MD5(wireshark-1.2.2.tar.bz2)=bb5c09b8cffd461ced4d3251fddb217b
SHA1(wireshark-1.2.2.tar.bz2)=ad73bf93096344341cd7c99614816555bebdbf45
RIPEMD160(wireshark-1.2.2.tar.bz2)=6adbd80e3027a63b456b971edba0185411d30546

wireshark-1.2.2.tar.gz: 19276130 bytes
MD5(wireshark-1.2.2.tar.gz)=3fa5f802313a4d8546bb2f50e769c369
SHA1(wireshark-1.2.2.tar.gz)=a07032b9b9e7c4875320c1b517101fd54e648662
RIPEMD160(wireshark-1.2.2.tar.gz)=5ba95f91ff60f367676ffec1d1370ffe493abf56

wireshark-win32-1.2.2.exe: 18298146 bytes
MD5(wireshark-win32-1.2.2.exe)=b5b79d22b1a399de102a6b4f616bac0e
SHA1(wireshark-win32-1.2.2.exe)=fea10ba291117d34f7d816b9ca861510d8da7312
RIPEMD160(wireshark-win32-1.2.2.exe)=7f9ab2f1225af8174f4f63c05dad54e7e20610af

wireshark-win64-1.2.2.exe: 14597960 bytes
MD5(wireshark-win64-1.2.2.exe)=ecb39661ed67c0064b5e8e92eb543205
SHA1(wireshark-win64-1.2.2.exe)=22c1e6a4bd903164fe149edfa97f6678786a466a
RIPEMD160(wireshark-win64-1.2.2.exe)=7b1d1b51eb771cdad210d20dc6cce714a9acb151

wireshark-1.2.2.u3p: 21419084 bytes
MD5(wireshark-1.2.2.u3p)=7a26ac834a46e9a464dca836b54c13a5
SHA1(wireshark-1.2.2.u3p)=ce810898c18103788052785fa125bd847dd18b16
RIPEMD160(wireshark-1.2.2.u3p)=b1788b8aea9b479095ee1fc75f750557c299dbfd

WiresharkPortable-1.2.2.paf.exe: 19117807 bytes
MD5(WiresharkPortable-1.2.2.paf.exe)=7effccf845cbb8c21954f6962d64c123
SHA1(WiresharkPortable-1.2.2.paf.exe)=0a89bb2b220e448d347702e009a42327c7e01397
RIPEMD160(WiresharkPortable-1.2.2.paf.exe)=b394e53219c944c5dc72100afe4e2d37c045d4f6

Wireshark 1.2.2 Intel.dmg: 42353160 bytes
MD5(Wireshark 1.2.2 Intel.dmg)=d8a63694add57967ac573d2109975151
SHA1(Wireshark 1.2.2 Intel.dmg)=756d353353409972528827b4202b818b6741afb8
RIPEMD160(Wireshark 1.2.2
Intel.dmg)=94588091d3ade3ee4cede3c4021e54e2c9679e1f

Wireshark 1.2.2 PPC.dmg: 44504677 bytes
MD5(Wireshark 1.2.2 PPC.dmg)=e7965c25ab01dcac96f87dfb27ff5b4f
SHA1(Wireshark 1.2.2 PPC.dmg)=96a104c8e9ecce14d7a03f7b7e5ca66aa16eb1d4
RIPEMD160(Wireshark 1.2.2 PPC.dmg)=46f5bbb7215537f42b38f048f43ea895502b6907

patch-wireshark-1.2.1-to-1.2.2.diff.bz2: 126942 bytes
MD5(patch-wireshark-1.2.1-to-1.2.2.diff.bz2)=40040a5aaefd86b0252d1d45219e3af1
SHA1(patch-wireshark-1.2.1-to-1.2.2.diff.bz2)=363c937abe1b22af19bc4cf4492f38718fbe0719
RIPEMD160(patch-wireshark-1.2.1-to-1.2.2.diff.bz2)=514161e0f7b5a5f74773034c3dd0d005272885b7

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

iEYEARECAAYFAkqv/W0ACgkQpw8IXSHylJqAIgCgzel36Vwx31uTMc3oRXgSoP3d
tokAnjy1eas1+El5fkJkglhqgSbf9Zgw
=dscf
-----END PGP SIGNATURE-----