ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-announce: [Wireshark-announce] Wireshark 3.6.4 is now available

Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Wed, 4 May 2022 11:59:09 -0700
I'm proud to announce the release of Wireshark 3.6.4.


 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]

  The Windows installers are now built with Visual Studio 2022.

  RPM packaging has been improved.

  Bug Fixes

   The following bugs have been fixed:

     • Build failure with GCC 7.5, Linux. Issue 17911[2].

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

     • IPFIX/cflow dissector asserts when varlen field length is zero.
       Issue 18010[4].

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

     • DHCPv6 Option 15 User-Class incorrectly parsed in Wireshark.
       Issue 18032[6].

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

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

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

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

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   CQL, DHCPv6, ICMPv6, IEEE 802.11, NAS-5GS, NetFlow/IPFIX, RDP, and
   UDS

  New and Updated Capture File Support

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

  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[11] 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[12] 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[13].

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

 Frequently Asked Questions

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

  Last updated 2022-05-04 16:32:25 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17779
   2. https://gitlab.com/wireshark/wireshark/-/issues/17911
   3. https://gitlab.com/wireshark/wireshark/-/issues/17952
   4. https://gitlab.com/wireshark/wireshark/-/issues/18010
   5. https://gitlab.com/wireshark/wireshark/-/issues/18030
   6. https://gitlab.com/wireshark/wireshark/-/issues/18032
   7. https://gitlab.com/wireshark/wireshark/-/issues/18033
   8. https://gitlab.com/wireshark/wireshark/-/issues/18035
   9. https://gitlab.com/wireshark/wireshark/-/issues/18038
  10. https://gitlab.com/wireshark/wireshark/-/issues/18050
  11. https://www.wireshark.org/download.html
  12. https://ask.wireshark.org/
  13. https://www.wireshark.org/lists/
  14. https://gitlab.com/wireshark/wireshark/-/issues
  15. https://www.wireshark.org/faq.html


Digests

wireshark-3.6.4.tar.xz: 39943660 bytes
SHA256(wireshark-3.6.4.tar.xz)=d55cfad4d490865cf2062f6b4af0cdfde85816ebad30455e3c3fda9899ab79a3
RIPEMD160(wireshark-3.6.4.tar.xz)=d8f4932d7e9abfca8ea8ed102f5550d7b0ae0387
SHA1(wireshark-3.6.4.tar.xz)=304307714159a497ad8e376ad2bfdab017320cc7

Wireshark-win32-3.6.4.exe: 61297360 bytes
SHA256(Wireshark-win32-3.6.4.exe)=20294191aaaf054385dfee093beaf255ceb8fa78af13bd0b0c1855b762721bf5
RIPEMD160(Wireshark-win32-3.6.4.exe)=a9f766f43caf6e2b6463e952b1d7b35e108f4a31
SHA1(Wireshark-win32-3.6.4.exe)=bf25844ad66a5d2d9e866dd88cbe2b46f93bf5c8

Wireshark-win64-3.6.4.exe: 77585248 bytes
SHA256(Wireshark-win64-3.6.4.exe)=0247e6d8e024cc8487370c964a44e9a7c6fcc022a1554f0832c83ad8fa9088a1
RIPEMD160(Wireshark-win64-3.6.4.exe)=198891dc2d0bf0a54df952edaf45d7abc875c575
SHA1(Wireshark-win64-3.6.4.exe)=d7ae2efa762063290ccd79b66437dfa157efe67e

Wireshark-win64-3.6.4.msi: 50880512 bytes
SHA256(Wireshark-win64-3.6.4.msi)=6cd6d6c0429329570ec41f569fedb9f58df64cccd01479c895eb450c74963da4
RIPEMD160(Wireshark-win64-3.6.4.msi)=85d752e94964cf4e8d209e482b8f7e12b9c6fda2
SHA1(Wireshark-win64-3.6.4.msi)=e7a7a7514667fda088c8bb7e5605a6dccff19026

Wireshark-win32-3.6.4.msi: 45568000 bytes
SHA256(Wireshark-win32-3.6.4.msi)=f32c32ae72a8da2590bc2d6f18b88b9d57c411af5df15a10083e29a6d143945f
RIPEMD160(Wireshark-win32-3.6.4.msi)=0199406d0efbd1f815f2fa1aa151aa69e53ca86e
SHA1(Wireshark-win32-3.6.4.msi)=1d1a8fbc60b93f341e586f9c4df1123bcfb0df67

WiresharkPortable64_3.6.4.paf.exe: 44352896 bytes
SHA256(WiresharkPortable64_3.6.4.paf.exe)=25880e9cc0e41b14288557945f8d0f34918ab788d642af6c226c2944c54a0db3
RIPEMD160(WiresharkPortable64_3.6.4.paf.exe)=23465115e3190307f9bc6201d1dde974a3ac4065
SHA1(WiresharkPortable64_3.6.4.paf.exe)=a5cc3d243161aff6a75cdda4535bc19d99e09502

WiresharkPortable32_3.6.4.paf.exe: 39598672 bytes
SHA256(WiresharkPortable32_3.6.4.paf.exe)=64eabd28b8015a40f92f53a7b7959066cb006be41f2fbe356d55fe4f5174ac72
RIPEMD160(WiresharkPortable32_3.6.4.paf.exe)=03a64b705d5105772781a7dcc13d5ea9e99c4484
SHA1(WiresharkPortable32_3.6.4.paf.exe)=85b53c4c6dc64f6357a9a60fff9f19500ea8bce4

Wireshark 3.6.4 Arm 64.dmg: 137410345 bytes
SHA256(Wireshark 3.6.4 Arm 64.dmg)=1f65940a6a56b338b8b7ce4eca9d29d329642e56898d59cf30e7da191caa68c2
RIPEMD160(Wireshark 3.6.4 Arm 64.dmg)=b1f427f3b9e7b8024e7c579f8bc84327eaeb37c7
SHA1(Wireshark 3.6.4 Arm 64.dmg)=d97ea7f67c773402d5ba47fa6aaf1e243d3d8247

Wireshark 3.6.4 Intel 64.dmg: 138908959 bytes
SHA256(Wireshark 3.6.4 Intel 64.dmg)=88cad2084766d5258d4e247b1f9b51a01ae5dda2bc697b541f2c442f3a239131
RIPEMD160(Wireshark 3.6.4 Intel 64.dmg)=8fd4b8edcecc1b77c4c9db94009da86e33cb2f81
SHA1(Wireshark 3.6.4 Intel 64.dmg)=887544863da8dc44927725319b4e2d51dbda402d

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