[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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


 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 bugs have been fixed:

     • Fuzz job crash output: fuzz-2022-01-19-7399.pcap Issue 17894[1].

     • TLS dissector incorrectly reports JA3 values Issue 17942[2].

     • "Wiki Protocol page" in packet details menu is broken - wiki
       pages not migrated to GitLab? Issue 17944[3].

     • Dissector bug, protocol PFCP display Flow Description IE value
       error in Additional Flow Description of PFD Management Request
       Message Issue 17951[4].

     • Bluetooth: Fails to open Log file for SCO connection Issue
       17964[5].

     • Fuzz job crash output: fuzz-2022-03-07-10896.pcap Issue 17984[6].

     • libwiretap: Save as ERF causes segmentation fault Issue 17989[7].

     • HTTP server returning multiple early hints shows too many
       responses in "Follow HTTP Stream" Issue 18006[8].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   CSN.1, HTTP, IEEE 802.11, NTLM SSP, PFCP, PKTLOG, SSDP, TLS, and USB
   HID

  New and Updated Capture File Support

   pcap and 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[9] 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[10] 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[11].

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

 Frequently Asked Questions

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

  Last updated 2022-03-23 16:42:51 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17894
   2. https://gitlab.com/wireshark/wireshark/-/issues/17942
   3. https://gitlab.com/wireshark/wireshark/-/issues/17944
   4. https://gitlab.com/wireshark/wireshark/-/issues/17951
   5. https://gitlab.com/wireshark/wireshark/-/issues/17964
   6. https://gitlab.com/wireshark/wireshark/-/issues/17984
   7. https://gitlab.com/wireshark/wireshark/-/issues/17989
   8. https://gitlab.com/wireshark/wireshark/-/issues/18006
   9. https://www.wireshark.org/download.html
  10. https://ask.wireshark.org/
  11. https://www.wireshark.org/lists/
  12. https://gitlab.com/wireshark/wireshark/-/issues
  13. https://www.wireshark.org/faq.html


Digests

wireshark-3.6.3.tar.xz: 39935892 bytes
SHA256(wireshark-3.6.3.tar.xz)=b60364a4c0068a10811ab3fd075ca6c1eb0e75d44600271b88a20ed93a2ef631
RIPEMD160(wireshark-3.6.3.tar.xz)=e34360909c9e4822595f6c96666171e1caef66b1
SHA1(wireshark-3.6.3.tar.xz)=72226ea907b660309f0d356fc967f75974a16047

Wireshark-win64-3.6.3.exe: 77475048 bytes
SHA256(Wireshark-win64-3.6.3.exe)=b87ee22f981c033e6a075193c2a9a4cf699ec1a5bde7ec4851b9344a27b73eb7
RIPEMD160(Wireshark-win64-3.6.3.exe)=4b9f661d85007ed6ecaaec8e5990dc12ea0b48d0
SHA1(Wireshark-win64-3.6.3.exe)=c6127feaf0b250ca52b6baa170a974a796db79e8

Wireshark-win32-3.6.3.exe: 61329928 bytes
SHA256(Wireshark-win32-3.6.3.exe)=8f7d298c06505948999a557cefda084015ca010a6b2812b36ec18726a5f65bfb
RIPEMD160(Wireshark-win32-3.6.3.exe)=641e074c3800e00d76a80b47aa0bd26a1c5a929f
SHA1(Wireshark-win32-3.6.3.exe)=1259590a55bb65eaa9f5186da42e80b0dadb824b

Wireshark-win32-3.6.3.msi: 45518848 bytes
SHA256(Wireshark-win32-3.6.3.msi)=d373d252723ffd357114b40e8e4292c4d447995c00b937cf3394f7c9a1ede185
RIPEMD160(Wireshark-win32-3.6.3.msi)=7cd384a11e113ceafea0e828e584f3d7f596f471
SHA1(Wireshark-win32-3.6.3.msi)=ebd6ea81ebf96df51cee5480a2938a25f1a4021b

Wireshark-win64-3.6.3.msi: 50798592 bytes
SHA256(Wireshark-win64-3.6.3.msi)=8ac14d26320751c938c70ba81fab3febb1a95c79588316c68757ec442fc92e1f
RIPEMD160(Wireshark-win64-3.6.3.msi)=19ceda5370f3177fcbc20144521e880f272fe0f6
SHA1(Wireshark-win64-3.6.3.msi)=93a38c6d688f3aecf126ed1b9efcf53fc6c7cd8f

WiresharkPortable32_3.6.3.paf.exe: 39538752 bytes
SHA256(WiresharkPortable32_3.6.3.paf.exe)=f2c1e026df966cdcbbb07fe215b42e63575e87d0e61728e917bab30aa1a6aed4
RIPEMD160(WiresharkPortable32_3.6.3.paf.exe)=950a4943a290b5c35b44cd57cb704a63a0a4dd52
SHA1(WiresharkPortable32_3.6.3.paf.exe)=f281e610da157f745d4dc7922d8cc0d7e64ebaa4

WiresharkPortable64_3.6.3.paf.exe: 44293192 bytes
SHA256(WiresharkPortable64_3.6.3.paf.exe)=169e1b389bc97f28e12d93643be6fc31ebcedce75f9e466645f5843ae4356075
RIPEMD160(WiresharkPortable64_3.6.3.paf.exe)=cc1bbd18d55e4447eafc079bb99c97c8cbf3d97a
SHA1(WiresharkPortable64_3.6.3.paf.exe)=6fde24cd7c98e4a79214a9fd820ca6d4392e6799

Wireshark 3.6.3 Arm 64.dmg: 137199813 bytes
SHA256(Wireshark 3.6.3 Arm 64.dmg)=d991168cc82683650ad171ae9e90a0f76a0aae17082e234bcd2ddf887b10c63f
RIPEMD160(Wireshark 3.6.3 Arm 64.dmg)=9842b95c269e442025ac411bf8c369c3ac04a3c1
SHA1(Wireshark 3.6.3 Arm 64.dmg)=106a200ec8af1e0f993f60a229ccc8ec875d9d2d

Wireshark 3.6.3 Intel 64.dmg: 138797493 bytes
SHA256(Wireshark 3.6.3 Intel 64.dmg)=7e46df85d4a2fcbbe774ce56ebe69988bc60a4d498feb13951778f7178b94981
RIPEMD160(Wireshark 3.6.3 Intel 64.dmg)=ae92e11c9b69ed8fd814e539d13beeda0bc828cd
SHA1(Wireshark 3.6.3 Intel 64.dmg)=58c56c6240e4fdd649d44727b5e7aad7a5870635

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