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

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 22 Apr 2014 11:52:23 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm proud to announce the release of Wireshark 1.8.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.

   The following bugs have been fixed:
     * Lua: trying to get/access a Preference before its
       registered causes a segfault ([1]Bug 9853)
     * Some value_string strings contain newlines. ([2]Bug 9878)
     * Tighten the NO_MORE_DATA_CHECK macros ([3]Bug 9932)

  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

   ANSI A, DVB-CI, IEEE 802.11, and MAC LTE

  New and Updated Capture File Support

   and There are no changes in this release.

  Getting Wireshark

   Wireshark source code and installation packages are available
   from [4]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 [5]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. ([6]Bug
   1419)

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

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

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

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

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

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

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

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

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

Getting Help

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

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

Frequently Asked Questions

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

   Last updated 2014-04-22 09:47:21 PDT

References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9853
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9878
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9932
   4. http://www.wireshark.org/download.html
   5. http://www.wireshark.org/download.html#thirdparty
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  10. https://wiki.wireshark.org/Development/Win64
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  16. http://ask.wireshark.org/
  17. http://www.wireshark.org/lists/
  18. http://www.wiresharktraining.com/
  19. http://www.wireshark.org/faq.html


Digests

wireshark-1.8.14.tar.bz2: 24158670 bytes
MD5(wireshark-1.8.14.tar.bz2)=e8b52a9bde82797faaa28c15a82be32d
SHA1(wireshark-1.8.14.tar.bz2)=ae68a3c38cb2ab97d046c8975b49fdf0c9a0304c
RIPEMD160(wireshark-1.8.14.tar.bz2)=5d0b9b214aec37cbe5ce5100f2cba038efcbd2af

Wireshark-win32-1.8.14.exe: 20782000 bytes
MD5(Wireshark-win32-1.8.14.exe)=136b7ca44c10b360cbc6979813c5889f
SHA1(Wireshark-win32-1.8.14.exe)=d387d77fafd2c922ec10575286f092afdb38d7df
RIPEMD160(Wireshark-win32-1.8.14.exe)=b43c964411d1ed471351467d6e19035d265296e2

Wireshark-win64-1.8.14.exe: 26444712 bytes
MD5(Wireshark-win64-1.8.14.exe)=a901f955aed49acce50831ebd74c389e
SHA1(Wireshark-win64-1.8.14.exe)=ea19b89340e0b9c96cdabd3a033687bfe9a2497f
RIPEMD160(Wireshark-win64-1.8.14.exe)=2e5139e20723436299a64d028933f6c9712b6795

Wireshark-1.8.14.u3p: 28482529 bytes
MD5(Wireshark-1.8.14.u3p)=3e5d718c62c149373d8a82ebd3b1024b
SHA1(Wireshark-1.8.14.u3p)=cab0bce27c7bbf869f0777fec9a402ec0b11173d
RIPEMD160(Wireshark-1.8.14.u3p)=9a3f38853ba3395f728135f43abcde302dd38593

WiresharkPortable-1.8.14.paf.exe: 21966656 bytes
MD5(WiresharkPortable-1.8.14.paf.exe)=ca3e441744cac55b66cc55270b3c6cb4
SHA1(WiresharkPortable-1.8.14.paf.exe)=ef28d791ba3ffa232444c88dbd1fbbaaadb94a82
RIPEMD160(WiresharkPortable-1.8.14.paf.exe)=2644bb939c379c87d76ff7b541da71fa99567529

Wireshark 1.8.14 Intel 32.dmg: 18358078 bytes
MD5(Wireshark 1.8.14 Intel 32.dmg)=8d2fa929f543ad01bd6533be0638c7d6
SHA1(Wireshark 1.8.14 Intel
32.dmg)=3755e06904916886ef37bedfa8303c53799e1438
RIPEMD160(Wireshark 1.8.14 Intel
32.dmg)=8a31090ebb9f81861d7eb9dae73b2b8a978a4865

Wireshark 1.8.14 PPC 32.dmg: 22825409 bytes
MD5(Wireshark 1.8.14 PPC 32.dmg)=5d39a6a109d5ee5af1ca63c431442fa4
SHA1(Wireshark 1.8.14 PPC 32.dmg)=11711ecee417f70bfe2c11c00cdeb4719108a7d1
RIPEMD160(Wireshark 1.8.14 PPC
32.dmg)=09b7e7c567124a351166e02caa06a916abe1a786

Wireshark 1.8.14 Intel 64.dmg: 21852231 bytes
MD5(Wireshark 1.8.14 Intel 64.dmg)=16f86293a17d3bdfced24d55fd920a0c
SHA1(Wireshark 1.8.14 Intel
64.dmg)=eede7be08bb5b1730bab97aec44d9c9dbff9d724
RIPEMD160(Wireshark 1.8.14 Intel
64.dmg)=5ea57e9dec570a384b8eed10d083ab0112a68bda

patch-wireshark-1.8.13-to-1.8.14.diff.bz2: 69501 bytes
MD5(patch-wireshark-1.8.13-to-1.8.14.diff.bz2)=f9879b90995a806bffa51fa99e2e14c8
SHA1(patch-wireshark-1.8.13-to-1.8.14.diff.bz2)=a9100c297f495f45df5a84e2d3339128c8caad1a
RIPEMD160(patch-wireshark-1.8.13-to-1.8.14.diff.bz2)=dfe39982326a15e15a2a0ea865a39cd0e6963f88
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlNWumcACgkQpw8IXSHylJpBCACfZX2KQEc43LICP/oM8oqmKrTW
HgoAn2zra1jJpGdw1tJ09YCHcqxtUb4W
=4QEP
-----END PGP SIGNATURE-----