[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 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:

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

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

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

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

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

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   CSN.1, HTTP, NTLMSSP, PFCP, and PKTLOG

  New and Updated Capture File Support

   pcap and pcapng

 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[6] 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 About → 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[7] 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[8].

  Issues and feature requests can be reported on the issue tracker[9].

 Frequently Asked Questions

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

  Last updated 2022-03-23 16:43:37 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17944
   2. https://gitlab.com/wireshark/wireshark/-/issues/17951
   3. https://gitlab.com/wireshark/wireshark/-/issues/17964
   4. https://gitlab.com/wireshark/wireshark/-/issues/17989
   5. https://gitlab.com/wireshark/wireshark/-/issues/18006
   6. https://www.wireshark.org/download.html#thirdparty
   7. https://ask.wireshark.org/
   8. https://www.wireshark.org/lists/
   9. https://gitlab.com/wireshark/wireshark/-/issues
  10. https://www.wireshark.org/faq.html


Digests

wireshark-3.4.13.tar.xz: 32373384 bytes
SHA256(wireshark-3.4.13.tar.xz)=58a21fe3c36517f56d6a77095dec67e2f09233176ac7cd4f48233cffe29e6e31
RIPEMD160(wireshark-3.4.13.tar.xz)=43e7cd68f832e43b44b57977e6b68d64cb90e196
SHA1(wireshark-3.4.13.tar.xz)=9bbfd8cdac44f7e6fdd1e5bfe94ab18b7d971e2d

Wireshark-win64-3.4.13.exe: 71585032 bytes
SHA256(Wireshark-win64-3.4.13.exe)=3b4f789174f367346bcaaf90f676b073b0bb251462bc49f7a73a0e6a0646d938
RIPEMD160(Wireshark-win64-3.4.13.exe)=f0d076d5d443f777b1a668eb07d0b5d742c7e0fa
SHA1(Wireshark-win64-3.4.13.exe)=076d02f40774e59a1a24370e1c1f309ace0c4bc7

Wireshark-win32-3.4.13.exe: 55559632 bytes
SHA256(Wireshark-win32-3.4.13.exe)=14ca5c4d9d3de1a70dcf1a0315be4a0ccefd2fe982876b86c7f5a842e343208f
RIPEMD160(Wireshark-win32-3.4.13.exe)=900d7b7a40932a8fc6cbda6c1bc9f9d47bed7b92
SHA1(Wireshark-win32-3.4.13.exe)=69e4126c539b359729addefd507165f3965bfcb5

Wireshark-win32-3.4.13.msi: 44154880 bytes
SHA256(Wireshark-win32-3.4.13.msi)=6262776729d8ea482f97b8ad405a967d81dee9838d15a1e92686e60f68dbff1f
RIPEMD160(Wireshark-win32-3.4.13.msi)=658460f7c27856911560f352c5a70b8bd5cc0f44
SHA1(Wireshark-win32-3.4.13.msi)=857b6544e744d0caf2354337c2c1ee3bbdf4361e

Wireshark-win64-3.4.13.msi: 49356800 bytes
SHA256(Wireshark-win64-3.4.13.msi)=294356ae08041d5fa63ccb84e9876e58961475ba6815b0bd0e5203a730d1cb1e
RIPEMD160(Wireshark-win64-3.4.13.msi)=73487560e7d6185842ce652bbec5e6f7e406c561
SHA1(Wireshark-win64-3.4.13.msi)=36ebf1c97890add30068aeda0380f4cfe50a2aff

WiresharkPortable_3.4.13.paf.exe: 38433504 bytes
SHA256(WiresharkPortable_3.4.13.paf.exe)=c2eb574480c3bbd41d95c76e8fc5735294fbdd90e5735517cbe2a610dac10f7c
RIPEMD160(WiresharkPortable_3.4.13.paf.exe)=ec92c675d67e02439d0e5a2986e2577cbaee3fee
SHA1(WiresharkPortable_3.4.13.paf.exe)=52901643f3a1ea0340c76c36eb7abb8b200d3c43

Wireshark 3.4.13 Intel 64.dmg: 131362044 bytes
SHA256(Wireshark 3.4.13 Intel 64.dmg)=b659cbdc6c9c6389bac8fa4061397b8175ef80e0effb838d77d728ae86afbd72
RIPEMD160(Wireshark 3.4.13 Intel 64.dmg)=e7f932ad77bd63e46bbc7a1196f0c881402654d8
SHA1(Wireshark 3.4.13 Intel 64.dmg)=356f68ae326f0e89afa04cbd37686d0a02d814df

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