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

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 11 Jan 2011 15:11:08 -0800
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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

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 FRAsse discovered that the MAC-LTE dissector could overflow a
       buffer. (Bug 5530)

       Versions affected: 1.2.0 to 1.2.13 and 1.4.0 to 1.4.2.

     o FRAsse discovered that the ENTTEC dissector could overflow a
       buffer. (Bug 5539)

       Versions affected: 1.2.0 to 1.2.13 and 1.4.0 to 1.4.2.

       CVE-2010-4538

   The following bugs have been fixed:

     o Menu and Title bars inaccessible using GTK2 (non-legacy) with
       two monitors. (Bug 553)

     o AMQP failed assertion. (Bug 4048)

     o Reassemble.c leaks memory for GLIB > 2.8. (Bug 4141)

     o Fuzz testing reports possible dissector bug: TCP. (Bug 4211)

     o LTE-PDCP UL and DL problem. (Bug 5505)

     o Buffer overflow in SNMP EngineID preferences. (Bug 5530)

  New and Updated Features

   There are no new features in this release.

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   AMQP, ASN.1 BER, Diameter, ENTTEC, LTE-PDCP, MAC-LTE, SAMR, SNMP,
   TCP, UNISTIM

  Updated Capture File Support

   VMS TCPtrace.

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 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)

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

Getting Help

   Community support is available on Wireshark's Q&A site and on the
   wireshark-users mailing list. Subscription information and
   archives for all of Wireshark's mailing lists can be found on the
   web site.

   Training is available from Wireshark University.

Frequently Asked Questions

   A complete FAQ is available on the Wireshark web site.


Digests

wireshark-1.2.14.tar.bz2: 15443875 bytes
MD5(wireshark-1.2.14.tar.bz2)=eb5130582d1db4fbb400138ba36e7d42
SHA1(wireshark-1.2.14.tar.bz2)=6b75c06af7a1d29c25b6a83fc18bc187a5109f9d
RIPEMD160(wireshark-1.2.14.tar.bz2)=0329d929c8ab7a181a713d48515b970a7b4a33d9

wireshark-1.2.14.tar.gz: 19533107 bytes
MD5(wireshark-1.2.14.tar.gz)=f25f4b6a212824643ab96b8b3d69fdd0
SHA1(wireshark-1.2.14.tar.gz)=3f62438462efe57644a37eb79571f71ecbd3497f
RIPEMD160(wireshark-1.2.14.tar.gz)=c02823a94a5592d001c0394d322f64e71ab6487e

wireshark-win32-1.2.14.exe: 18147801 bytes
MD5(wireshark-win32-1.2.14.exe)=45d4e64d49f076bd3cfd700664cc50bf
SHA1(wireshark-win32-1.2.14.exe)=106fbcbf53c2f4fec9bdc8d97c6c87678fb02136
RIPEMD160(wireshark-win32-1.2.14.exe)=453610dd333fffb31513924b14bd89001ac443df

wireshark-win64-1.2.14.exe: 20415078 bytes
MD5(wireshark-win64-1.2.14.exe)=4f626f355e99f258123f7684ce639ab8
SHA1(wireshark-win64-1.2.14.exe)=584bd8a1a1b75d29719f9a801fdb4be14f21e63d
RIPEMD160(wireshark-win64-1.2.14.exe)=b7abb32f2f45054869a365a7c180821f1d8eda16

wireshark-1.2.14.u3p: 21261000 bytes
MD5(wireshark-1.2.14.u3p)=0f72e0836d1622e4da6c81287a7fe81a
SHA1(wireshark-1.2.14.u3p)=f081d6edbf0c7063539cfa683b4dcc1a62c487a2
RIPEMD160(wireshark-1.2.14.u3p)=3d281bea85737aaaf52b557e7e6459d98877666c

WiresharkPortable-1.2.14.paf.exe: 18869570 bytes
MD5(WiresharkPortable-1.2.14.paf.exe)=fba546b78af9e5dc1a4bdee218769805
SHA1(WiresharkPortable-1.2.14.paf.exe)=b59bba952f5a59fd5febd933d462d8a27042b875
RIPEMD160(WiresharkPortable-1.2.14.paf.exe)=b5b45316860202248aba1e12b5bb7104a9f68dbf

Wireshark 1.2.14 Intel.dmg: 41473016 bytes
MD5(Wireshark 1.2.14 Intel.dmg)=2cb9e1a3feef235e7706bf3a1369e53c
SHA1(Wireshark 1.2.14 Intel.dmg)=07ca19f82c6a561fd0ecf185891b72aaf10ed9f6
RIPEMD160(Wireshark 1.2.14
Intel.dmg)=f837077ff8cba0bf32b6c4b8eafacd47bd080248

Wireshark 1.2.14 PPC.dmg: 44755156 bytes
MD5(Wireshark 1.2.14 PPC.dmg)=6c2acd316f2ca2944d27f8c4347524e2
SHA1(Wireshark 1.2.14 PPC.dmg)=c5c318f36badac4a68031f92126cc46b957a3479
RIPEMD160(Wireshark 1.2.14 PPC.dmg)=8fbdd650cf7b01c6313f6202b7a3a72d11f74ff8

patch-wireshark-1.2.13-to-1.2.14.diff.bz2: 108775 bytes
MD5(patch-wireshark-1.2.13-to-1.2.14.diff.bz2)=46eb1cc52bdfc0a2b5e1a2bd7e00ce86
SHA1(patch-wireshark-1.2.13-to-1.2.14.diff.bz2)=12f302cb16cfc2fa067a4e588c2c5f8116b12f6c
RIPEMD160(patch-wireshark-1.2.13-to-1.2.14.diff.bz2)=9b8244cba32ad7b18c90c6d02e689fdbf85e2d8f
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0s44wACgkQpw8IXSHylJr2bACfVBRCnGf+MCpqlLXWup6ihI1t
edkAnRTXqrBYZXnH8bUFp+GnYtRDJuf1
=KJ5a
-----END PGP SIGNATURE-----