Wireshark · Wireshark-announce: [Wireshark-announce] Wireshark 3.2.14 is now available

[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.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 bugs have been fixed:

     • Macro filters can’t handle escaped characters Issue 17160[1].

     • Display filter crashes Wireshark Issue 17316[2].

     • IEEE-1588 Signalling Unicast TLV incorrectly reported as being
       malformed Issue 17355[3].

  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

   DNP, ProtoBuf, PTP, and TACACS

  New and Updated Capture File Support

   Ascend, ERF, K12, NetScaler, and pcapng

 Getting Wireshark

  Wireshark source code and installation packages are available from
  https://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[4] 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.

 Getting Help

  The User’s Guide, manual pages and various other documentation can be
  found at https://www.wireshark.org/docs/

  Community support is available on Wireshark’s Q&A site[5] 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[6].

  Issues and feature requests can be reported on the issue tracker[7].

 Frequently Asked Questions

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

  Last updated 2021-06-02 17:49:53 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17160
   2. https://gitlab.com/wireshark/wireshark/-/issues/17316
   3. https://gitlab.com/wireshark/wireshark/-/issues/17355
   4. https://www.wireshark.org/download.html#thirdparty
   5. https://ask.wireshark.org/
   6. https://www.wireshark.org/lists/
   7. https://gitlab.com/wireshark/wireshark/-/issues
   8. https://www.wireshark.org/faq.html


Digests

wireshark-3.2.14.tar.xz: 31523896 bytes
SHA256(wireshark-3.2.14.tar.xz)=7af69dd760486c1bf01aea541aadd8135ca5da040eb9f18e0c90cd14b0fc27ea
RIPEMD160(wireshark-3.2.14.tar.xz)=d168d03d0dbca603037c884e05a1f75c3e80b558
SHA1(wireshark-3.2.14.tar.xz)=583e5e6b6116967d872ab4b7832f69a1e28390ea

Wireshark-win32-3.2.14.exe: 54925712 bytes
SHA256(Wireshark-win32-3.2.14.exe)=4cf32a4ff48f921b1771df3f515a57118e1f7f5656e7390fca8824f2c7b77f75
RIPEMD160(Wireshark-win32-3.2.14.exe)=40b9c3f97ddb3dab574398115f7168c449a60ccd
SHA1(Wireshark-win32-3.2.14.exe)=1d032e4c305973a332bdddc0b44d5342257dc653

Wireshark-win64-3.2.14.exe: 60087384 bytes
SHA256(Wireshark-win64-3.2.14.exe)=ec4d218d5105a5c00a735d5bc28af38df49849c81fbcc3c2d8219c47cf1c0108
RIPEMD160(Wireshark-win64-3.2.14.exe)=c51f315b4c4f3d5a9d413e306ac0013d933eef20
SHA1(Wireshark-win64-3.2.14.exe)=4d14d35af0e09d0b47e0c8ec840b573fde36b074

Wireshark-win64-3.2.14.msi: 48447488 bytes
SHA256(Wireshark-win64-3.2.14.msi)=d2eadc5e9993436e3e5778e10728a0b4d14b97a0defab587e6d2b6d0c2af35c0
RIPEMD160(Wireshark-win64-3.2.14.msi)=82387132896e7b0ce7fdbfbf76ba845b2e6af306
SHA1(Wireshark-win64-3.2.14.msi)=b41baf54e9bc91b41c523ead8c105c17bf40fcd4

Wireshark-win32-3.2.14.msi: 43171840 bytes
SHA256(Wireshark-win32-3.2.14.msi)=d35c2297642fe2b146fa6d14beb24747204bfd4306c4b1b3b510231dcb09da23
RIPEMD160(Wireshark-win32-3.2.14.msi)=325a96df749c30b2fa76d161feab7727dc2315ce
SHA1(Wireshark-win32-3.2.14.msi)=252c56cb8a2425fd092dcd50f2a1dea65698b901

WiresharkPortable_3.2.14.paf.exe: 36786272 bytes
SHA256(WiresharkPortable_3.2.14.paf.exe)=5b75891ba6af502c91e5cdc9296ee094e3f9460525079608f1ef10891c20d3f8
RIPEMD160(WiresharkPortable_3.2.14.paf.exe)=6961ccfa7bcc5c188947a31b07b2bb74cc22c223
SHA1(WiresharkPortable_3.2.14.paf.exe)=d862c182fca7f17db96d9bf79a4e14f5a8bb5e5f

Wireshark 3.2.14 Intel 64.dmg: 100461385 bytes
SHA256(Wireshark 3.2.14 Intel 64.dmg)=9d3228579f9bc42542fa29de5e3dc698c359e9d261df953f1a34a60c16e507e4
RIPEMD160(Wireshark 3.2.14 Intel 64.dmg)=bb6ece2e448e44a5ef96d66b72b62ce7ac132559
SHA1(Wireshark 3.2.14 Intel 64.dmg)=d2c6c60d3b51fa63018e8984e561765e35f82683

You can validate these hashes using the following commands (among others):

    Windows: certutil -hashfile Wireshark-win64-x.y.z.exe SHA256
    Linux (GNU Coreutils): sha256sum wireshark-x.y.z.tar.xz
    macOS: shasum -a 256 "Wireshark x.y.z Intel 64.dmg"
    Other: openssl sha256 wireshark-x.y.z.tar.xz

Attachment: OpenPGP_signature
Description: OpenPGP digital signature