Wireshark-announce: [Wireshark-announce] Wireshark 1.2.13 is now available
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <[email protected]>
Date: Fri, 19 Nov 2010 12:24:08 -0800
I'm proud to announce the release of Wireshark 1.2.13.

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 Nephi Johnson of BreakingPoint discovered that the LDSS
       dissector could overflow a buffer. (Bug 5318)

       Versions affected: 1.2.0 to 1.2.12 and 1.4.0 to 1.4.1.

   The following bugs have been fixed:

     o File-Open Display Filter is overwritten by Save-As Filename.
       (Bug 3894)

     o GTK-ERROR can occur in packets when there are multiple
       Netbios/SMB headers in a single frame. (Bug 5289)

     o IO Graph Time of Day times incorrect for filtered data. (Bug
       5340)

  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

   BOOTP, LDSS

  Updated Capture File Support

   There are no new or updated capture file formats in this release.

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)

   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.

   Commercial support, training, and development services are
   available from CACE Technologies.

   Training is available from Wireshark University.

Frequently Asked Questions

   A complete FAQ is available on the Wireshark web site.


Digests

wireshark-1.2.13.tar.bz2: 15423242 bytes
MD5(wireshark-1.2.13.tar.bz2)=bd8ca6bd7e818dcc46a7137f9c3dfdce
SHA1(wireshark-1.2.13.tar.bz2)=81bf3dc1736fa740ec98d85c50a05498b80a8d74
RIPEMD160(wireshark-1.2.13.tar.bz2)=0665a3d0c50099c67f3401f31dda1cb121c399db

wireshark-1.2.13.tar.gz: 19512648 bytes
MD5(wireshark-1.2.13.tar.gz)=8383375cc241c96247d57579eefc0710
SHA1(wireshark-1.2.13.tar.gz)=e4a1550a2f98fa49926ed6fe10e2fc28e4bf7221
RIPEMD160(wireshark-1.2.13.tar.gz)=ebdc29f83546391cb8eb4056ef686f3ced21215f

wireshark-win32-1.2.13.exe: 18150990 bytes
MD5(wireshark-win32-1.2.13.exe)=00008c4ab4ddc80bdb5681fe019a3e09
SHA1(wireshark-win32-1.2.13.exe)=567a1a92107216b6237960b08c148379bac9fd07
RIPEMD160(wireshark-win32-1.2.13.exe)=4db35ce46aa6645ca644a9debe299bb014b32588

wireshark-win64-1.2.13.exe: 20415266 bytes
MD5(wireshark-win64-1.2.13.exe)=d095ed81b4c7a51c08b0eddf6f8d68af
SHA1(wireshark-win64-1.2.13.exe)=bc79a7c524fc999bab83bbb1ae3d9de390eda9cf
RIPEMD160(wireshark-win64-1.2.13.exe)=de7c993d98668024aa5c199b4f1a6563ef5f3904

wireshark-1.2.13.u3p: 21260119 bytes
MD5(wireshark-1.2.13.u3p)=cdf16acc1ae6a165b50e2388d48329a5
SHA1(wireshark-1.2.13.u3p)=7a3c15bee979724bfcbd58a51507fbfa95aec21a
RIPEMD160(wireshark-1.2.13.u3p)=f07ef0c2a85587ec0eb60ff95b9296bcdc078b90

WiresharkPortable-1.2.13.paf.exe: 18877597 bytes
MD5(WiresharkPortable-1.2.13.paf.exe)=6f55037818ea707372182fb364411010
SHA1(WiresharkPortable-1.2.13.paf.exe)=9f200d874050321f8ffd2c106510460b8ae93b61
RIPEMD160(WiresharkPortable-1.2.13.paf.exe)=cf8fd8c6ad87cf122017f54539cf041e3c6c5618

Wireshark 1.2.13 Intel.dmg: 42587855 bytes
MD5(Wireshark 1.2.13 Intel.dmg)=8a11412267f3b013b153b2131c4bca67
SHA1(Wireshark 1.2.13 Intel.dmg)=3642e1f3904760bae8ec364fda3ffa8f5bd79dff
RIPEMD160(Wireshark 1.2.13
Intel.dmg)=68e3fa5ceb02b1aa55b76338daacdd11cb07f210

Wireshark 1.2.13 PPC.dmg: 44761185 bytes
MD5(Wireshark 1.2.13 PPC.dmg)=5ee4f19f98c3b98ade13e58a00d39ec1
SHA1(Wireshark 1.2.13 PPC.dmg)=f1615f97a164f413f6a019297a9de294228dcd45
RIPEMD160(Wireshark 1.2.13 PPC.dmg)=26b0d400ab7cfe630747edce8787368b4c8b2d54

patch-wireshark-1.2.12-to-1.2.13.diff.bz2: 57175 bytes
MD5(patch-wireshark-1.2.12-to-1.2.13.diff.bz2)=a856fbafd6d37437f65b7dc1b7b3a89d
SHA1(patch-wireshark-1.2.12-to-1.2.13.diff.bz2)=ac722375454de3604959e1b7dd25aaaf8fb7ae72
RIPEMD160(patch-wireshark-1.2.12-to-1.2.13.diff.bz2)=679642ad2b6161418d3c5e0a0dc7f3f93c12471d