[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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


 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

   This release fixes an installation issue on Windows which was
   introduced in the 3.6.4 release. Issue 18077[2].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

  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[3] 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[4] 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[5].

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

 Frequently Asked Questions

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

  Last updated 2022-05-05 00:57:58 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17779
   2. https://gitlab.com/wireshark/wireshark/-/issues/18077
   3. https://www.wireshark.org/download.html
   4. https://ask.wireshark.org/
   5. https://www.wireshark.org/lists/
   6. https://gitlab.com/wireshark/wireshark/-/issues
   7. https://www.wireshark.org/faq.html


Digests

wireshark-3.6.5.tar.xz: 39939340 bytes
SHA256(wireshark-3.6.5.tar.xz)=a2d741d60ff3516137d4b9f38cdc07eee54a56ec36046f4c3afee6bfb4f6eaa1
RIPEMD160(wireshark-3.6.5.tar.xz)=ef68cb3f47f01c56854f7d82f1820c4a83b9a8ff
SHA1(wireshark-3.6.5.tar.xz)=72499f56ed70434256054b8d81a1c71bee38c9c2

Wireshark-win64-3.6.5.exe: 77462328 bytes
SHA256(Wireshark-win64-3.6.5.exe)=042b59e0d28ec9147dd3f94c3f3c82e6e5c3303de50a8fbc06878de9bd3b5e68
RIPEMD160(Wireshark-win64-3.6.5.exe)=ba047c3ca45335da9851a11ac5943ea5637b7d4c
SHA1(Wireshark-win64-3.6.5.exe)=d68cdc4e44371fd126bd667158f9c1d35e3ef3c4

Wireshark-win32-3.6.5.exe: 61306800 bytes
SHA256(Wireshark-win32-3.6.5.exe)=be617a51a4c6075c57b8335d198cb91712547e06ab599f2e8a8cfc89bab2d20f
RIPEMD160(Wireshark-win32-3.6.5.exe)=f535691c7c65254ce8db884b8dbe167580a19561
SHA1(Wireshark-win32-3.6.5.exe)=dc069d760a75aece90f57b0df9c90f192036c3a2

Wireshark-win32-3.6.5.msi: 45551616 bytes
SHA256(Wireshark-win32-3.6.5.msi)=5a8e94b0ca3b253929ae367b232d9611cd5519d1abe162dfdce1981f2eeee87b
RIPEMD160(Wireshark-win32-3.6.5.msi)=f2cc9ed54c71511846dad9ebb471c0b455a32409
SHA1(Wireshark-win32-3.6.5.msi)=ba133f299564b405e5fd2a8d2409031fac76769f

Wireshark-win64-3.6.5.msi: 51052544 bytes
SHA256(Wireshark-win64-3.6.5.msi)=a7f3d8b733c97b7533c4aac54379c82f1049b49c5f30d7e6cc29d7281976fa32
RIPEMD160(Wireshark-win64-3.6.5.msi)=20546e63326f3cc12cf9b613b0f410aa0a7de5fc
SHA1(Wireshark-win64-3.6.5.msi)=f51792ac96de7402523a9891f9eddd88ff0ed0f4

WiresharkPortable64_3.6.5.paf.exe: 44398000 bytes
SHA256(WiresharkPortable64_3.6.5.paf.exe)=2bce179d26396b3818b73515db842dff05c19169b2f3761e8a1793a085a960f9
RIPEMD160(WiresharkPortable64_3.6.5.paf.exe)=3f7b0d5a2732d39828e5745dad72e187385d622e
SHA1(WiresharkPortable64_3.6.5.paf.exe)=a7cf792c88be1acbc637fa443b0267b46ffb819f

WiresharkPortable32_3.6.5.paf.exe: 39606144 bytes
SHA256(WiresharkPortable32_3.6.5.paf.exe)=d25a90d53f070af0e8ecfd9e0e5b75f2418eca4332e0c2450c23b9859781202c
RIPEMD160(WiresharkPortable32_3.6.5.paf.exe)=062591b9648fa4e0184a5c1adadcd7200644363f
SHA1(WiresharkPortable32_3.6.5.paf.exe)=b967b11ddbb25b02b9cacc6ef3bc5f666303b877

Wireshark 3.6.5 Arm 64.dmg: 137410154 bytes
SHA256(Wireshark 3.6.5 Arm 64.dmg)=805364720514e8d8938f48bb0c84da4b3ab3e82fdb3d1167a4189ddf8a7801cb
RIPEMD160(Wireshark 3.6.5 Arm 64.dmg)=a46f1e6892762946f81a8a887c221b9e7666dd0a
SHA1(Wireshark 3.6.5 Arm 64.dmg)=cd8317f35ad50e820ae78a055fd9158256dcfaf9

Wireshark 3.6.5 Intel 64.dmg: 138906477 bytes
SHA256(Wireshark 3.6.5 Intel 64.dmg)=585f2ac9eea45c69384f700bfb8a6d009fab40f43e4ca699fe3018b5161a8db8
RIPEMD160(Wireshark 3.6.5 Intel 64.dmg)=0da6dbd7528db874e1068089536762b28806e95b
SHA1(Wireshark 3.6.5 Intel 64.dmg)=e611ff5cedaa415710542e513e3121b34064c970

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