[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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


 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 now ship with Npcap 1.60. They previously
  shipped with Npcap 1.55.

  Bug Fixes

   The following bugs have been fixed:

     • TLS: RSA decryption fails with Extended Master Secret and
       renegotiation Issue 18059[2].

     • "dfilter" file on Windows adds carriage returns, and requires
       line feeds Issue 18082[3].

     • Npcap bundled version needs a bump to v1.60 for Windows 11
       compatibility Issue 18084[4].

     • "Browse" button in Prefs/Name Resolution/MaxMind crashes
       Wireshark on macOS Issue 18088[5].

     • TFTP: some packets are not recognized as TFTP packets with 3.6.5
       Issue 18122[6].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   DTLS, F5 Capture Information, F5 Ethernet Trailer, FlexRay, MBIM,
   TFTP, TLS, and ZigBee ZCL

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

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

 Frequently Asked Questions

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

  Last updated 2022-06-15 16:14:54 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17779
   2. https://gitlab.com/wireshark/wireshark/-/issues/18059
   3. https://gitlab.com/wireshark/wireshark/-/issues/18082
   4. https://gitlab.com/wireshark/wireshark/-/issues/18084
   5. https://gitlab.com/wireshark/wireshark/-/issues/18088
   6. https://gitlab.com/wireshark/wireshark/-/issues/18122
   7. https://www.wireshark.org/download.html
   8. https://ask.wireshark.org/
   9. https://www.wireshark.org/lists/
  10. https://gitlab.com/wireshark/wireshark/-/issues
  11. https://www.wireshark.org/faq.html


Digests

wireshark-3.6.6.tar.xz: 39950276 bytes
SHA256(wireshark-3.6.6.tar.xz)=beba27aeb4d3bb78df6202e88dda69e1dba9b0561044957bcac47e68b6ac28ba
RIPEMD160(wireshark-3.6.6.tar.xz)=6d017615bb57c53b223947893a59584c8b317c87
SHA1(wireshark-3.6.6.tar.xz)=2c28cda3f70396e0524d604f329665475d5b44e9

Wireshark-win32-3.6.6.exe: 61058080 bytes
SHA256(Wireshark-win32-3.6.6.exe)=c006fb0e279e28701e31420381f76efdbbfeacdb2be91b8acb2c6517ff98fa98
RIPEMD160(Wireshark-win32-3.6.6.exe)=c0b212691d0589e3416b68587464db3ec7b14a25
SHA1(Wireshark-win32-3.6.6.exe)=ad1a6f663f3341ea70bdebcc13de3670a0f6cbde

Wireshark-win64-3.6.6.exe: 77235824 bytes
SHA256(Wireshark-win64-3.6.6.exe)=abce9b1004ddd992cb6ffe80e755919bcd12646b008163bde6a7d684aa6b9374
RIPEMD160(Wireshark-win64-3.6.6.exe)=487c47b8451321f3ea0bd9ad1867108066f1b496
SHA1(Wireshark-win64-3.6.6.exe)=18bf15e9b126b82b60d4c17c5c2395464ad9238c

Wireshark-win32-3.6.6.msi: 45621248 bytes
SHA256(Wireshark-win32-3.6.6.msi)=1d3df54f1cb7bf6a01678ab9e7b7f993ae38349b4c8b3fc93e3d2afc1f96b5b0
RIPEMD160(Wireshark-win32-3.6.6.msi)=5f1bd7db4458bf1e883648a3cb54848b0219858f
SHA1(Wireshark-win32-3.6.6.msi)=c8f767fea89c953bfd5bbd1547adb22834ce7748

Wireshark-win64-3.6.6.msi: 51056640 bytes
SHA256(Wireshark-win64-3.6.6.msi)=fb101ece0f01df008edc56c87aeaa75a4c077dc6608252e67572734a9b83ffd0
RIPEMD160(Wireshark-win64-3.6.6.msi)=c5a8b201eca3081b259d65d7d601d892576e8eb7
SHA1(Wireshark-win64-3.6.6.msi)=6834fe4425e39b03bebaec3a74881f67968a3062

WiresharkPortable32_3.6.6.paf.exe: 39616520 bytes
SHA256(WiresharkPortable32_3.6.6.paf.exe)=197466968e20770d44a9624e093f91121db9e9bbed5586c769ae92cf372b1b97
RIPEMD160(WiresharkPortable32_3.6.6.paf.exe)=cfe50e7c097b7b11bbcaa4fec60aec59d83bbaae
SHA1(WiresharkPortable32_3.6.6.paf.exe)=11106bfc0ec2566b48c22e4e783e8ec21298c667

WiresharkPortable64_3.6.6.paf.exe: 44377552 bytes
SHA256(WiresharkPortable64_3.6.6.paf.exe)=85542fe11d1a3a4b21155f8f6f8b83b57c94c38e20d780524c370b4e2448e303
RIPEMD160(WiresharkPortable64_3.6.6.paf.exe)=068905d55663e78bc0e9d1ca5fd4e03df3be8b43
SHA1(WiresharkPortable64_3.6.6.paf.exe)=d9fa33dd8c94d978666c6e79dacbbb65072d5904

Wireshark 3.6.6 Arm 64.dmg: 137500386 bytes
SHA256(Wireshark 3.6.6 Arm 64.dmg)=f6c0a0b122828a3b3bf6fbe7aa857e629649e1396d79a188ceba052270880e0b
RIPEMD160(Wireshark 3.6.6 Arm 64.dmg)=0a5b9c096f4c62790873b5dabe99540338d14319
SHA1(Wireshark 3.6.6 Arm 64.dmg)=60a56b6d044a1146e410ff2f972ccbf248ac10d7

Wireshark 3.6.6 Intel 64.dmg: 139200462 bytes
SHA256(Wireshark 3.6.6 Intel 64.dmg)=1ddd2b1fc9a8de008c09c02a2179f4280e8f1ac925a7e1d2ec9b4f0fc41f7614
RIPEMD160(Wireshark 3.6.6 Intel 64.dmg)=9e8c68947837d93e102d4962c8555f20ee21d15d
SHA1(Wireshark 3.6.6 Intel 64.dmg)=bc4f953a731d0485e8ff0875486b22a75da65813

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