[Gerald Combs <gerald@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.4.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

  The Windows installers now ship with Npcap 1.31. They previously
  shipped with Npcap 1.10.

  The Windows installers now ship with Qt 5.15.2. They previously
  shipped with Qt 5.12.1.

  Bug Fixes

     • wnpa-sec-2021-04[1] DVB-S2-BB dissector infinite loop

   The following bugs have been fixed:

     • Macro filters can’t handle escaped characters Issue 17160[2].

     • Display filter crashes Wireshark Issue 17316[3].

     • IEEE-1588 Signalling Unicast TLV incorrectly reported as being
       malformed Issue 17355[4].

     • IETF QUIC TLS decryption error with extraneous packets during the
       handshake Issue 17383[5].

     • Statistics → Resolved Addresses: multi-protocol (TCP/UDP/…​)
       ports not displayed Issue 17395[6].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   DNP, DVB-S2-BB, ProtoBuf, PTP, QUIC, RANAP, and TACACS

  New and Updated Capture File Support

   Ascend, ERF, K12, NetScaler, 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[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 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[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].

  Issues 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 2021-06-02 17:49:35 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2021-04
   2. https://gitlab.com/wireshark/wireshark/-/issues/17160
   3. https://gitlab.com/wireshark/wireshark/-/issues/17316
   4. https://gitlab.com/wireshark/wireshark/-/issues/17355
   5. https://gitlab.com/wireshark/wireshark/-/issues/17383
   6. https://gitlab.com/wireshark/wireshark/-/issues/17395
   7. https://www.wireshark.org/download.html#thirdparty
   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.4.6.tar.xz: 32304604 bytes
SHA256(wireshark-3.4.6.tar.xz)=12a678208f8cb009e6b9d96026e41a6ef03c7ad086b9e1029f42053b249b4628
RIPEMD160(wireshark-3.4.6.tar.xz)=a2e4ab6cdd044495a5e91da23fa1a3d45a17ff39
SHA1(wireshark-3.4.6.tar.xz)=20596183210daeb0070ae43716529caf81c6187a

Wireshark-win64-3.4.6.exe: 61382664 bytes
SHA256(Wireshark-win64-3.4.6.exe)=9021124cd54bbd3301dcd98dbfa32f989ce9631e37cb652c2722bb8a3e561a33
RIPEMD160(Wireshark-win64-3.4.6.exe)=8aa15a4a183b18471643e2cbdbe87d7985797571
SHA1(Wireshark-win64-3.4.6.exe)=7d1686b5850bb2606a257895e3b03fa66d86981d

Wireshark-win32-3.4.6.exe: 56435872 bytes
SHA256(Wireshark-win32-3.4.6.exe)=702d61e63e5496fa7c952b97652cf2455b378b46ca1c808d7f5201bfddb51062
RIPEMD160(Wireshark-win32-3.4.6.exe)=9be64e53ba99f2c36883aa2aac7463a1c467854a
SHA1(Wireshark-win32-3.4.6.exe)=1a3070bb23b31af92b0ac18af7b162aaf4fba6e7

Wireshark-win32-3.4.6.msi: 44642304 bytes
SHA256(Wireshark-win32-3.4.6.msi)=7bcf63fcff3ede139c52f60452bd6f6137052f1f8669cbee3eec4f477becee16
RIPEMD160(Wireshark-win32-3.4.6.msi)=f66801be334f5dedbd28ed68801485930af1f6a7
SHA1(Wireshark-win32-3.4.6.msi)=f8a7231a0709e462b62c051aac723f9043d2fc8f

Wireshark-win64-3.4.6.msi: 49688576 bytes
SHA256(Wireshark-win64-3.4.6.msi)=75f42ee5663079d91cf5f48be0217ac9d97b404ef2f3c5f54639dc1635a943a8
RIPEMD160(Wireshark-win64-3.4.6.msi)=235a1950976dc20e34dc8a61ecf69010408530f3
SHA1(Wireshark-win64-3.4.6.msi)=b8a2969ca69195c132ee150f8aec5b706552be32

WiresharkPortable_3.4.6.paf.exe: 38306544 bytes
SHA256(WiresharkPortable_3.4.6.paf.exe)=5c886584ed761a011c4db01340bc28b1d1b421d2ec5cf00c6298d8944a019339
RIPEMD160(WiresharkPortable_3.4.6.paf.exe)=19f87ccc00f9e88a69714f1632716342f8a71296
SHA1(WiresharkPortable_3.4.6.paf.exe)=9cbb37cf7af0e496b7db30c3a995c029f228dfae

Wireshark 3.4.6 Intel 64.dmg: 130991548 bytes
SHA256(Wireshark 3.4.6 Intel 64.dmg)=fbf27fb0947cd2fefca7896158552e6f3b90b863afb46a75780ff0b24d649ce2
RIPEMD160(Wireshark 3.4.6 Intel 64.dmg)=4bdfc674018dea626b2aff8b92aa48607bcdecec
SHA1(Wireshark 3.4.6 Intel 64.dmg)=236603462a1972a0a0f974dc06eeafa43bce7e6a

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 Intel 64.dmg"
    Other: openssl sha256 wireshark-x.y.z.tar.xz

Attachment: OpenPGP_signature
Description: OpenPGP digital signature