[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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

     • RDP dissected as SSL. Issue 17952[1].

     • Interface statistics are not updated if some interfaces are
       hidden. Issue 18023[2].

     • 802.11ax HE PHY "Device Class" dissected incorrectly. Issue
       18030[3].

     • ICMPv6 dissector: PREF64 option parsing only works for prefix
       length 96. Issue 18033[4].

     • Switch macOS updater to Sparkle 2. Issue 18035[5].

     • CQL timestamp dissector displays the wrong timestamp. Issue
       18038[6].

     • Unable to dissect 802.11ax Target Wake Time (TWT) packets. Issue
       18050[7].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   CQL, DHCPv6, ICMPv6, IEEE 802.11, and RDP

  New and Updated Capture File Support

   There is no new or updated capture file support in this release.

 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[8] 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[9] 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[10].

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

 Frequently Asked Questions

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

  Last updated 2022-05-04 16:31:51 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17952
   2. https://gitlab.com/wireshark/wireshark/-/issues/18023
   3. https://gitlab.com/wireshark/wireshark/-/issues/18030
   4. https://gitlab.com/wireshark/wireshark/-/issues/18033
   5. https://gitlab.com/wireshark/wireshark/-/issues/18035
   6. https://gitlab.com/wireshark/wireshark/-/issues/18038
   7. https://gitlab.com/wireshark/wireshark/-/issues/18050
   8. https://www.wireshark.org/download.html#thirdparty
   9. https://ask.wireshark.org/
  10. https://www.wireshark.org/lists/
  11. https://gitlab.com/wireshark/wireshark/-/issues
  12. https://www.wireshark.org/faq.html


Digests

wireshark-3.4.14.tar.xz: 32380036 bytes
SHA256(wireshark-3.4.14.tar.xz)=32b0d0772e942d2d66cb3757bfb5027e53a6ddfbc908b65be5f3048f7a082dee
RIPEMD160(wireshark-3.4.14.tar.xz)=d0c45f9d21dc127da15e7bd5adf87f3a77e5f17d
SHA1(wireshark-3.4.14.tar.xz)=514900283a6f20c6676133c9a61ee57352cd5c0e

Wireshark-win64-3.4.14.exe: 71631032 bytes
SHA256(Wireshark-win64-3.4.14.exe)=7b5649760b3e53836effdb95b6660dfdc762fe527416e19459988e0e689c9d27
RIPEMD160(Wireshark-win64-3.4.14.exe)=3b767b84495334e272e772f57f344633c7e73c93
SHA1(Wireshark-win64-3.4.14.exe)=076d7a0f3a507d24d6cf73218188254308df5c0a

Wireshark-win32-3.4.14.exe: 55596968 bytes
SHA256(Wireshark-win32-3.4.14.exe)=b36f3e5b3210a5e320e16073ce00676fbb235d965c9f56ff80f80d059743011f
RIPEMD160(Wireshark-win32-3.4.14.exe)=bc81da654f123c0012a360c95b61525a35c670f0
SHA1(Wireshark-win32-3.4.14.exe)=871123268264be13445224f2d491d3e4b046b997

Wireshark-win64-3.4.14.msi: 49401856 bytes
SHA256(Wireshark-win64-3.4.14.msi)=eea70295a64e3ad5d0c91de56c3327a79cb9557694bf5bd5273d74ba28cdb56f
RIPEMD160(Wireshark-win64-3.4.14.msi)=347b603f6b00c3406dfac80ac563514185c09b93
SHA1(Wireshark-win64-3.4.14.msi)=e5a0038fffbb6dfe31034db36c5938385688f6ea

Wireshark-win32-3.4.14.msi: 44220416 bytes
SHA256(Wireshark-win32-3.4.14.msi)=2f8c0d234e6d1bb5141fe86b58b8c0af968f085b918a9e7bf7dc696c26acc3e8
RIPEMD160(Wireshark-win32-3.4.14.msi)=b4f0188758dd9ec67f29793cf028c867cc9eed91
SHA1(Wireshark-win32-3.4.14.msi)=d91c48055983aca748d6831ba7b9fc58eaac63db

WiresharkPortable_3.4.14.paf.exe: 38475472 bytes
SHA256(WiresharkPortable_3.4.14.paf.exe)=36d17ab20534da868e925790584ce0ef956baaf4faec010120dc4e2b76e489ce
RIPEMD160(WiresharkPortable_3.4.14.paf.exe)=a0be2ee9b6d1c5a901ee0e8facbf8ce940e1c235
SHA1(WiresharkPortable_3.4.14.paf.exe)=f518f9d7fbf6c1862d98f21f8786408e8943afe1

Wireshark 3.4.14 Intel 64.dmg: 131733466 bytes
SHA256(Wireshark 3.4.14 Intel 64.dmg)=567ae3d99b1ff2f9d3910b5de984b932a23fc8169f68d0a76a4e2d576fb4262a
RIPEMD160(Wireshark 3.4.14 Intel 64.dmg)=daa68e0de2b18b2a359cd2e02a574ae635fc41c2
SHA1(Wireshark 3.4.14 Intel 64.dmg)=ff934fa7fa28948da15b646d2ff440528596a8f4

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 Arm 64.dmg"
    Other: openssl sha256 wireshark-x.y.z.tar.xz

Attachment: OpenPGP_signature
Description: OpenPGP digital signature