[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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

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 Huzaifa Sidhpurwala of the Red Hat Security Response Team
       discovered that Wireshark could free an uninitialized pointer
       while reading a malformed pcap-ng file. (Bug 5652)

       Versions affected: 1.2.0 to 1.2.14 and 1.4.0 to 1.4.3.

       CVE-2011-0538

     o Huzaifa Sidhpurwala of the Red Hat Security Response Team
       discovered that a large packet length in a pcap-ng file could
       crash Wireshark. (Bug 5661)

       Versions affected: 1.2.0 to 1.2.14 and 1.4.0 to 1.4.3.

     o Wireshark could overflow a buffer while reading a Nokia DCT3
       trace file. (Bug 5661)

       Versions affected: 1.2.0 to 1.2.14 and 1.4.0 to 1.4.3.

       CVE-2011-0713

     o joernchen of Phenoelit discovered that the LDAP and SMB
       dissectors could overflow the stack. (Bug 5717)

       Versions affected: 1.2.0 to 1.2.14 and 1.4.0 to 1.4.3. (Prior
       versions including 1.0.x are also affected.)

     o Xiaopeng Zhang of Fortinet's Fortiguard Labs discovered that
       large LDAP Filter strings can consume excessive amounts of
       memory. (Bug 5732)

       Versions affected: 1.2.0 to 1.2.14 and 1.4.0 to 1.4.3. (Prior
       versions including 1.0.x are also affected.)

   The following bugs have been fixed:

     o Wireshark Crashing by pressing 2 Buttons. (Bug 4645)

     o Potential access violation when writing to LANalyzer files.
       (Bug 5698)

  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

   LDAP, SMB

  Updated Capture File Support

   LANalyzer, Nokia DCT3, Pcap-ng

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.15.tar.bz2: 15449507 bytes
MD5(wireshark-1.2.15.tar.bz2)=e247f7620c270eb165871c760150fc8a
SHA1(wireshark-1.2.15.tar.bz2)=cca64dd713e8836451c57b32d93e927863454d19
RIPEMD160(wireshark-1.2.15.tar.bz2)=0393308cf7edeb9c275cc744383f18a07357d35e

wireshark-1.2.15.tar.gz: 19552909 bytes
MD5(wireshark-1.2.15.tar.gz)=872bd6cd88dac0ad5f09ef8a7609260e
SHA1(wireshark-1.2.15.tar.gz)=4b7482fe7b98204d5b84185334eab724088ab456
RIPEMD160(wireshark-1.2.15.tar.gz)=aedb3bb016aedf537bfa37345d9ee9167afe16cb

wireshark-win32-1.2.15.exe: 18154450 bytes
MD5(wireshark-win32-1.2.15.exe)=6e10863a6549dd394b6fdb74deb1135f
SHA1(wireshark-win32-1.2.15.exe)=b5de955a303be42d8c2bd31e622ea0405d6990b9
RIPEMD160(wireshark-win32-1.2.15.exe)=22c1b3fe4d572148125d9efe3010c57d90532445

wireshark-win64-1.2.15.exe: 20427484 bytes
MD5(wireshark-win64-1.2.15.exe)=634bbcdf21cc0544c1935b20a4a75e59
SHA1(wireshark-win64-1.2.15.exe)=f3be7a888109ecaaf8f97edf9ea710b8a22e7494
RIPEMD160(wireshark-win64-1.2.15.exe)=560d75a9a5a692c7dd590c9ff66786fceb24fcd2

wireshark-1.2.15.u3p: 21280242 bytes
MD5(wireshark-1.2.15.u3p)=09c7172752f16227f1b5c10bf5f78695
SHA1(wireshark-1.2.15.u3p)=329ac2b37b233898fd69028352c1b00169fd63a1
RIPEMD160(wireshark-1.2.15.u3p)=de25d72cba9d115be27d89d3b539352ee0d89b51

WiresharkPortable-1.2.15.paf.exe: 18876567 bytes
MD5(WiresharkPortable-1.2.15.paf.exe)=efdea5138baf47b3b10d0362b2d716d4
SHA1(WiresharkPortable-1.2.15.paf.exe)=2206d7bf1b3c1694bb89442484e9b88714cd1920
RIPEMD160(WiresharkPortable-1.2.15.paf.exe)=3c66d355459c81930bb7a5177a42627e04866805

Wireshark 1.2.15 Intel.dmg: 42610727 bytes
MD5(Wireshark 1.2.15 Intel.dmg)=36f57ecff0bdaaa2d97edd24a5e7fb2e
SHA1(Wireshark 1.2.15 Intel.dmg)=e86a4145024a66b4208394af70cf1876f4d3ed2b
RIPEMD160(Wireshark 1.2.15
Intel.dmg)=d61f78238e2a6b2140d2202abb654c9f24c82538

Wireshark 1.2.15 PPC.dmg: 44766947 bytes
MD5(Wireshark 1.2.15 PPC.dmg)=d771292d55b5f77663be984f2ae8bb92
SHA1(Wireshark 1.2.15 PPC.dmg)=2a2c6debe0cd51a711e58ee08df6c8315718d567
RIPEMD160(Wireshark 1.2.15 PPC.dmg)=418639b81c0cadec7fd4d4bc0534e6a1cde5952d

patch-wireshark-1.2.14-to-1.2.15.diff.bz2: 80437 bytes
MD5(patch-wireshark-1.2.14-to-1.2.15.diff.bz2)=ff8b1312c8b7dd79030b3100db51f3d3
SHA1(patch-wireshark-1.2.14-to-1.2.15.diff.bz2)=12be68e595390278e8d2375d9ef2b8204b14956a
RIPEMD160(patch-wireshark-1.2.14-to-1.2.15.diff.bz2)=efcb9703e797841329d866cdc3f307a522028caf