Wireshark-announce: [Wireshark-announce] Wireshark 3.6.8 is now available
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <[email protected]>
Date: Wed, 7 Sep 2022 11:28:18 -0700
I'm proud to announce the release of Wireshark 3.6.8.


 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

 Note: This is the last release branch with support for 32-bit Windows.
 Updates will no longer be available after May 22, 2024 for that
 platform. Issue 17779[1]

  Bug Fixes

   The following vulnerabilities have been fixed:

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

   The following bugs have been fixed:

     • TCAP Malformed exception on externally re-assembled packet Issue
       10515[4].

     • Extended 3GPP-GPRS-Negotiated-QoS-profile strings decoded
       incompletely Issue 10688[5].

     • HTTP2 dissector decodes first SSL record only Issue 11173[6].

     • L2TP improvements - cookie length detection, UDP encapsulation
       and more Issue 16565[7].

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

     • ISUP/BICC parameter summary text duplication Issue 18094[9].

     • Running rpm-setup.sh shows missing packages that Centos does not
       need Issue 18166[10].

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

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

     • BGP dissector bug Issue 18248[13].

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

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

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

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

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   BGP, BICC, BT ATT, CBSP, Couchbase, F5 Ethernet Trailer, Frame, GTP,
   GTP (prime), IPsec, ISUP, L2TP, NAS-5GS, Protobuf, SCCP, TCP, and TLS

  New and Updated Capture File Support

   pcap, pcapng

  New File Format Decoding Support

   There is no new or updated file format 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[18] 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 "Help › About
  Wireshark › Folders" or `tshark -G 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[19] 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[20].

  Bugs and feature requests can be reported on the issue tracker[21].

 Frequently Asked Questions

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

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17779
   2. https://www.wireshark.org/security/wnpa-sec-2022-06
   3. https://gitlab.com/wireshark/wireshark/-/issues/18307
   4. https://gitlab.com/wireshark/wireshark/-/issues/10515
   5. https://gitlab.com/wireshark/wireshark/-/issues/10688
   6. https://gitlab.com/wireshark/wireshark/-/issues/11173
   7. https://gitlab.com/wireshark/wireshark/-/issues/16565
   8. https://gitlab.com/wireshark/wireshark/-/issues/18021
   9. https://gitlab.com/wireshark/wireshark/-/issues/18094
  10. https://gitlab.com/wireshark/wireshark/-/issues/18166
  11. https://gitlab.com/wireshark/wireshark/-/issues/18234
  12. https://gitlab.com/wireshark/wireshark/-/issues/18235
  13. https://gitlab.com/wireshark/wireshark/-/issues/18248
  14. https://gitlab.com/wireshark/wireshark/-/issues/18254
  15. https://gitlab.com/wireshark/wireshark/-/issues/18267
  16. https://gitlab.com/wireshark/wireshark/-/issues/18312
  17. https://gitlab.com/wireshark/wireshark/-/issues/18313
  18. https://www.wireshark.org/download.html
  19. https://ask.wireshark.org/
  20. https://www.wireshark.org/lists/
  21. https://gitlab.com/wireshark/wireshark/-/issues
  22. https://www.wireshark.org/faq.html


Digests

wireshark-3.6.8.tar.xz: 39942580 bytes
SHA256(wireshark-3.6.8.tar.xz)=67ab23ee09a646ab8cc0ddcc985209f24f253337461e3d9644c6cfe1c097260c
SHA1(wireshark-3.6.8.tar.xz)=e4b2cb5703f9d6cf0934469a2e8a2426cb308dad

Wireshark-win64-3.6.8.exe: 77301408 bytes
SHA256(Wireshark-win64-3.6.8.exe)=17ce19def77592d4c0fb0b680e77e4712dd6c8c4af79c6d58a281eb509a4f34b
SHA1(Wireshark-win64-3.6.8.exe)=2160b0a85bf8131c7e9a912a4364f5019f98000d

Wireshark-win32-3.6.8.exe: 61106552 bytes
SHA256(Wireshark-win32-3.6.8.exe)=332aff4889f73ee1daf656e3411554685796a51f8059e2cd531bb60fb754799c
SHA1(Wireshark-win32-3.6.8.exe)=a74431156d5f85c0cd51094200ebb32a603be79e

Wireshark-win64-3.6.8.msi: 51019776 bytes
SHA256(Wireshark-win64-3.6.8.msi)=f0558d461a902cccdf35f44462e4bc9a0726ca8b0a90ceaa5854b10f0d49c325
SHA1(Wireshark-win64-3.6.8.msi)=358696df8ebe3eaba626d0e59c5364577f225f36

Wireshark-win32-3.6.8.msi: 45662208 bytes
SHA256(Wireshark-win32-3.6.8.msi)=1028e5f498acf941fad4aa387f7bdbcc419389d1241e02333fa824ec48a87b7b
SHA1(Wireshark-win32-3.6.8.msi)=163404a19abbc20bd435c037c0d84b3fd4d886e9

WiresharkPortable32_3.6.8.paf.exe: 39683296 bytes
SHA256(WiresharkPortable32_3.6.8.paf.exe)=2a28cf101f35e8f6a53c3d973779d5ea940488b09a9b9ca09f4567c9da27dfa1
SHA1(WiresharkPortable32_3.6.8.paf.exe)=ee1746e9a2bae5f148278f8834084ae716661474

WiresharkPortable64_3.6.8.paf.exe: 44428832 bytes
SHA256(WiresharkPortable64_3.6.8.paf.exe)=dd3c3a488c4aafc8ed87d7ed3a2abd64c2f8ee47eaf0676895d4b3ce986b0903
SHA1(WiresharkPortable64_3.6.8.paf.exe)=5a616cf739a7675eaef8f9c18117153f4f5e186f

Wireshark 3.6.8 Arm 64.dmg: 137659040 bytes
SHA256(Wireshark 3.6.8 Arm 64.dmg)=ae1735b05050da20d1a8d2d5c209bcd20743745ac23473bf034631f5b963970a
SHA1(Wireshark 3.6.8 Arm 64.dmg)=b5b6108ae0166b6d8b53473598e4fded1f57abb2

Wireshark 3.6.8 Intel 64.dmg: 139390338 bytes
SHA256(Wireshark 3.6.8 Intel 64.dmg)=c1e54f1af933486ac60da94bb1a366df5125959ef416e1a93c2a2fb9de78efa0
SHA1(Wireshark 3.6.8 Intel 64.dmg)=8bf551f8e6c98ccdba95af3cc5912772af857f79

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