[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.4.16.


  This is expected to be the final release of the 3.4 branch.

 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:

     • wnpa-sec-2022-06[1] F5 Ethernet Trailer dissector infinite loop.
       Issue 18307[2].

   The following bugs have been fixed:

     • USB Truncation of URB_isochronous in frames Issue 18021[3].

     • IPX/IPX RIP: Crash on expand subtree Issue 18234[4].

     • Qt: A file or packet comment that is too large will corrupt the
       pcapng file Issue 18235[5].

     • Wrong interpretation of the cbsp.rep_period field in
       epan/dissectors/packet-gsm_cbsp.c Issue 18254[6].

     • Assertion due to incorrect mask for btatt.battery_power_state.*
       Issue 18267[7].

     • Qt: Expert Info dialog not showing Malformed Frame when Frame
       length is less than captured length Issue 18312[8].

     • Wireshark and tshark become non-responsive when reading certain
       packets Issue 18313[9].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   BT ATT, CBSP, Couchbase, F5 Ethernet Trailer, Frame, NAS-5GS, and
   Protobuf

  New and Updated Capture File Support

   pcap, 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[10] 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[11] 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[12].

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

 Frequently Asked Questions

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

 References

   1. https://www.wireshark.org/security/wnpa-sec-2022-06
   2. https://gitlab.com/wireshark/wireshark/-/issues/18307
   3. https://gitlab.com/wireshark/wireshark/-/issues/18021
   4. https://gitlab.com/wireshark/wireshark/-/issues/18234
   5. https://gitlab.com/wireshark/wireshark/-/issues/18235
   6. https://gitlab.com/wireshark/wireshark/-/issues/18254
   7. https://gitlab.com/wireshark/wireshark/-/issues/18267
   8. https://gitlab.com/wireshark/wireshark/-/issues/18312
   9. https://gitlab.com/wireshark/wireshark/-/issues/18313
  10. https://www.wireshark.org/download.html#thirdparty
  11. https://ask.wireshark.org/
  12. https://www.wireshark.org/lists/
  13. https://gitlab.com/wireshark/wireshark/-/issues
  14. https://www.wireshark.org/faq.html


Digests

wireshark-3.4.16.tar.xz: 32404124 bytes
SHA256(wireshark-3.4.16.tar.xz)=6acb3155b89b65bcdbcdac7a9e6a59013a6e21d8ae6a8249a9af4fe9ce3d91ba
SHA1(wireshark-3.4.16.tar.xz)=b0e64d5fdd6701106d94bdc8f59dd40a34c7c807

Wireshark-win64-3.4.16.exe: 71671504 bytes
SHA256(Wireshark-win64-3.4.16.exe)=cb1f9c2eb389d119eff83022fe83179d8a68a504cfa1bb0198db665211a1a46d
SHA1(Wireshark-win64-3.4.16.exe)=a9404ff422266bbb22da82f98e4a97a9f873de83

Wireshark-win32-3.4.16.exe: 55655920 bytes
SHA256(Wireshark-win32-3.4.16.exe)=3a7dd34b732fb421da14ebf42e7c905ab45441474cd8a398b1ea4d098c2ec2d5
SHA1(Wireshark-win32-3.4.16.exe)=9816e67b3429853495a5f5bde6c29970d6e313e6

Wireshark-win64-3.4.16.msi: 49451008 bytes
SHA256(Wireshark-win64-3.4.16.msi)=ccd4d1a081c9f4b8b647d40f502b442e2a992ead0101174786c57e2bd5500638
SHA1(Wireshark-win64-3.4.16.msi)=ea463b597854dd8677406d2657ccd968a4879d31

Wireshark-win32-3.4.16.msi: 44281856 bytes
SHA256(Wireshark-win32-3.4.16.msi)=378d3546ff37a52d47fbda55288c0641268b94e6c6a3fbafecb917c8ae3843d4
SHA1(Wireshark-win32-3.4.16.msi)=2e873fe4fb474fbf594c5d99d4808c5ecad62865

WiresharkPortable_3.4.16.paf.exe: 38545784 bytes
SHA256(WiresharkPortable_3.4.16.paf.exe)=98cdc061664ff02d2c16b29878c14ab0bc954c8bcc9b182c60510b89a46997da
SHA1(WiresharkPortable_3.4.16.paf.exe)=2261850cf9ee7c46ecff9c2cf156aa84a969e914

Wireshark 3.4.16 Intel 64.dmg: 131805768 bytes
SHA256(Wireshark 3.4.16 Intel 64.dmg)=6d3cc30616e1e8b2272e3f95f2b861818766b363f4668f75797126493d0902f1
SHA1(Wireshark 3.4.16 Intel 64.dmg)=314711d3cb4c1bd78173c9dca734d9cdf77993b9

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