Wireshark-users: [Wireshark-users] Wireshark 1.8.13 is now available

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Fri, 07 Mar 2014 11:49:49 -0800
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm proud to announce the release of Wireshark 1.8.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.
     * [1]wnpa-sec-2014-01
       The NFS dissector could crash. Discovered by Moshe Kaplan.
       ([2]Bug 9672)
       Versions affected: 1.10.0 to 1.10.5, 1.8.0 to 1.8.12
       [3]CVE-2014-2281
     * [4]wnpa-sec-2014-03
       The RLC dissector could crash. ([5]Bug 9730)
       Versions affected: 1.10.0 to 1.10.5, 1.8.0 to 1.8.12
       [6]CVE-2014-2283
     * [7]wnpa-sec-2014-04
       The MPEG file parser could overflow a buffer. Discovered by
       Wesley Neelen. ([8]Bug 9843)
       Versions affected: 1.10.0 to 1.10.5, 1.8.0 to 1.8.12
       [9]CVE-2014-2299

   The following bugs have been fixed:
     * Customized OUI is not recognized correctly during
       dissection. ([10]Bug 9122)
     * MPLS dissector no longer registers itself in "ppp.protocol"
       table. ([11]Bug 9492)
     * Wireshark stops showing new packets but dumpcap keeps
       writing them to the temp file. ([12]Bug 9571)
     * Homeplug dissector bug: STATUS_ACCESS_VIOLATION: dissector
       accessed an invalid memory address. ([13]Bug 9578)
     * DMX-CHAN disector does not clear strbuf between rows.
       ([14]Bug 9598)
     * Dissector bug, protocol SDP: proto.c:4214: failed assertion
       "length >= 0". ([15]Bug 9633)
     * SMPP field source_telematics_id field length different from
       spec. ([16]Bug 9649)
     * GTPv1-C / MM Context / Authentication quintuplet / RAND is
       not correct. ([17]Bug 9722)
     * nas-eps dissector: CS Service notification dissection stops
       after Paging identity IE. ([18]Bug 9789)

  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

   AppleTalk, BSSGP, DMX-CHAN, DSI, DVB-CI, ESS, GSM BSSMAP, GSM
   BSSMAP LE, GSM CBS, GSM SMS, GTPv1, HomePlug, IEEE 802a, MPLS,
   NAS-EPS, NFS, SGSAP, SMPP, T.124, and TETRA

  New and Updated Capture File Support

   MPEG, NG Sniffer, and pcap-ng

  Getting Wireshark

   Wireshark source code and installation packages are available
   from [19]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 [20]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

   Dumpcap might not quit if Wireshark or TShark crashes. ([21]Bug
   1419)

   The BER dissector might infinitely loop. ([22]Bug 1516)

   Capture filters aren't applied when capturing from named pipes.
   ([23]Bug 1814)

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

   The 64-bit Windows installer does not support Kerberos
   decryption. ([25]Win64 development page)

   Application crash when changing real-time option. ([26]Bug
   4035)

   Hex pane display issue after startup. ([27]Bug 4056)

   Packet list rows are oversized. ([28]Bug 4357)

   Summary pane selected frame highlighting not maintained.
   ([29]Bug 4445)

   Wireshark and TShark will display incorrect delta times in some
   cases. ([30]Bug 4985)
     __________________________________________________________

Getting Help

   Community support is available on [31]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 [32]the web site.

   Official Wireshark training and certification are available
   from [33]Wireshark University.
     __________________________________________________________

Frequently Asked Questions

   A complete FAQ is available on the [34]Wireshark web site.
     __________________________________________________________

   Last updated 2014-03-07 10:09:55 PST

References

   1. https://www.wireshark.org/security/wnpa-sec-2014-01.html
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9672
   3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-2281
   4. https://www.wireshark.org/security/wnpa-sec-2014-03.html
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9730
   6. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-2283
   7. https://www.wireshark.org/security/wnpa-sec-2014-04.html
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9843
   9. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-2299
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9122
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9492
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9571
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9578
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9598
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9633
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9649
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9722
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9789
  19. http://www.wireshark.org/download.html
  20. http://www.wireshark.org/download.html#thirdparty
  21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  25. https://wiki.wireshark.org/Development/Win64
  26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056
  28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
  29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445
  30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  31. http://ask.wireshark.org/
  32. http://www.wireshark.org/lists/
  33. http://www.wiresharktraining.com/
  34. http://www.wireshark.org/faq.html


Digests

wireshark-1.8.13.tar.bz2: 24150627 bytes
MD5(wireshark-1.8.13.tar.bz2)=4c0b4d7983e0db1724b7728c0c6bcae7
SHA1(wireshark-1.8.13.tar.bz2)=ac2215ed2d97c344f3fdf0d365b3791f89aa0564
RIPEMD160(wireshark-1.8.13.tar.bz2)=56b7b64fb3ce5d2e485536c0a3a86a6e9bcf5cdb

Wireshark-win32-1.8.13.exe: 20775688 bytes
MD5(Wireshark-win32-1.8.13.exe)=7f084053a85f1fc22b6a05669f48dc17
SHA1(Wireshark-win32-1.8.13.exe)=cee82933d3abb90f7bac16c90152f35bee75f786
RIPEMD160(Wireshark-win32-1.8.13.exe)=268b6c27f75d59db029d7f8905efb15d9d06ce63

Wireshark-win64-1.8.13.exe: 26434600 bytes
MD5(Wireshark-win64-1.8.13.exe)=34c42250eed69fc5b77c4ae2c0c22795
SHA1(Wireshark-win64-1.8.13.exe)=bc2fd5f22acff21d3e63d055e71d37a30fd05546
RIPEMD160(Wireshark-win64-1.8.13.exe)=1bee8c791ff70523714bb91eeb74e82d1990fbb9

Wireshark-1.8.13.u3p: 28476033 bytes
MD5(Wireshark-1.8.13.u3p)=e2d9f7d738f636b66fdbccba7cfdd0d7
SHA1(Wireshark-1.8.13.u3p)=d33fc68d60efb77c368648d72d5b141b39ddf83f
RIPEMD160(Wireshark-1.8.13.u3p)=d2a486925d43053237152328d737ae7453030cea

WiresharkPortable-1.8.13.paf.exe: 21957552 bytes
MD5(WiresharkPortable-1.8.13.paf.exe)=ad39b6f08527847c137016968aaa74ed
SHA1(WiresharkPortable-1.8.13.paf.exe)=cf286e1c314f99db8001a2967a8b662b4539586a
RIPEMD160(WiresharkPortable-1.8.13.paf.exe)=8a4f40b8c48ad7f4796bb72dc564b5bfa584907e

Wireshark 1.8.13 Intel 64.dmg: 21845528 bytes
MD5(Wireshark 1.8.13 Intel 64.dmg)=9301969869d06706da0a0f2154493ca1
SHA1(Wireshark 1.8.13 Intel
64.dmg)=22a4434e20058a8c211ecdf7cba8c73221e23447
RIPEMD160(Wireshark 1.8.13 Intel
64.dmg)=8dc0712731f31da8459d10b4d21e8575812b8480

Wireshark 1.8.13 PPC 32.dmg: 22799229 bytes
MD5(Wireshark 1.8.13 PPC 32.dmg)=ee73397dd19a7cb8c38aaae6d6bb75b2
SHA1(Wireshark 1.8.13 PPC 32.dmg)=63fb67b535ab0ab1b04f05b471e1729e511d9122
RIPEMD160(Wireshark 1.8.13 PPC
32.dmg)=655a73c282004ac8773e7d6858b21dd3e454b2dd

Wireshark 1.8.13 Intel 32.dmg: 18334536 bytes
MD5(Wireshark 1.8.13 Intel 32.dmg)=82ab3c4e011551b7d005971b3f645b13
SHA1(Wireshark 1.8.13 Intel
32.dmg)=7ccea4424cf74f53be0a3a38a36a2e01154bc728
RIPEMD160(Wireshark 1.8.13 Intel
32.dmg)=bc4cb947e03c2528ca2a368f39181c867509b7bd

patch-wireshark-1.8.12-to-1.8.13.diff.bz2: 370452 bytes
MD5(patch-wireshark-1.8.12-to-1.8.13.diff.bz2)=961ddf3b92d436fc7dd1e19c1c78aed0
SHA1(patch-wireshark-1.8.12-to-1.8.13.diff.bz2)=95f88d5033c30076b0dd7642c18337c14640b6eb
RIPEMD160(patch-wireshark-1.8.12-to-1.8.13.diff.bz2)=136f82b6872313cc860220dca5f09d0056f61ed3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMaIt0ACgkQpw8IXSHylJpQ8wCfSel1B+2gF5sHGIl0unazZpQ3
Z3EAoMNMNC9hbd2ZQxeJPSMDnM77s/1y
=pZiw
-----END PGP SIGNATURE-----