Wireshark · Wireshark-users: [Wireshark-users] Wireshark 3.4.2 is now available

[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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


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

     • wnpa-sec-2020-20[1] QUIC dissector crash Bug 17073[2].

   The following bugs have been fixed:

  New and Updated Features

     • IETF QUIC TLS decryption errors when packets are coalesced with
       random data Bug 16914[3].

     • QUIC: missing dissection of some coalesced SH packets Bug
       17011[4].

     • macos-setup.sh can’t find SDK on macOS Big Sur, as it went to 11
       Bug 17043[5].

     • Mapping endpoints in browser ⇒ Map file error Bug 17074[6].

     • Wireshark 3.4.1 hangs on startup on macOS Big Sur 11.0.1 Bug
       17075[7].

     • False expect error seen on FCoE frames (not seen with older
       release wireshark 1.2.18) Bug 17084[8].

     • Several libraries missing in 3.4.1 and 3.2.9 installers for macOS
       Bug 17086[9].

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   DOCSIS, FC-dNS, FC-SWILS, FCoE, QUIC, SNMP, and USBHID

  New and Updated Capture File Support

   There is no new or updated capture file 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[10] 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’sQ&A site[11] 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[12].

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

 Frequently Asked Questions

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

  Last updated 2020-12-18 18:22:48 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2020-20
   2. https://gitlab.com/wireshark/wireshark/-/issues/17073
   3. https://gitlab.com/wireshark/wireshark/-/issues/16914
   4. https://gitlab.com/wireshark/wireshark/-/issues/17011
   5. https://gitlab.com/wireshark/wireshark/-/issues/17043
   6. https://gitlab.com/wireshark/wireshark/-/issues/17074
   7. https://gitlab.com/wireshark/wireshark/-/issues/17075
   8. https://gitlab.com/wireshark/wireshark/-/issues/17084
   9. https://gitlab.com/wireshark/wireshark/-/issues/17086
  10. https://www.wireshark.org/download.html#thirdparty
  11. https://ask.wireshark.org/
  12. https://www.wireshark.org/lists/
  13. https://gitlab.com/wireshark/wireshark/-/issues
  14. https://www.wireshark.org/faq.html


Digests

wireshark-3.4.2.tar.xz: 32465900 bytes
SHA256(wireshark-3.4.2.tar.xz)=de9868729e426a469baabd8d444240d84fa5445020e92c842dd19afd0d47a4c4
RIPEMD160(wireshark-3.4.2.tar.xz)=53a02106b0f23e50b1108d93772464974b2b37be
SHA1(wireshark-3.4.2.tar.xz)=b33276e4e6c3d6a057da3b569b58316330a5f3e3

Wireshark-win32-3.4.2.exe: 56527344 bytes
SHA256(Wireshark-win32-3.4.2.exe)=c2d6db4ece2cfd724c88602c7fc2fa336279b4bce7644d6e3174e29042871db8
RIPEMD160(Wireshark-win32-3.4.2.exe)=474760431d6d426d7c12f6e8e8f02d208a14d41e
SHA1(Wireshark-win32-3.4.2.exe)=4900bde2fd1ae2b9af52c971dbeb4bfb0e6523c0

Wireshark-win64-3.4.2.exe: 61483296 bytes
SHA256(Wireshark-win64-3.4.2.exe)=faa98f833e10b450c24e42a42292ff894c36b97aec526bf259796488888fd57c
RIPEMD160(Wireshark-win64-3.4.2.exe)=6c3752f93eb157b52f9aa1943dbc73b0099c804d
SHA1(Wireshark-win64-3.4.2.exe)=bf855c8fdeec43d1bea32a195a6b142c6697cca3

Wireshark-win64-3.4.2.msi: 49790976 bytes
SHA256(Wireshark-win64-3.4.2.msi)=c84d78b7803d09a6e9bc7a88e3c99c08f52fb6d825855c92edad8762dec7f38d
RIPEMD160(Wireshark-win64-3.4.2.msi)=f81204059cc5990014dd842c9f753b584a0e53b7
SHA1(Wireshark-win64-3.4.2.msi)=b9786daac33922af095a333c53508864a8cb0a57

Wireshark-win32-3.4.2.msi: 44736512 bytes
SHA256(Wireshark-win32-3.4.2.msi)=1aad705038039287768607e87e586bad23dad739a995de58bf3e3c192ad5a9ec
RIPEMD160(Wireshark-win32-3.4.2.msi)=5035b35162027a3970a38e4c983f9599648e68a1
SHA1(Wireshark-win32-3.4.2.msi)=9198f71c384edf8c6366969941e5406da8e32149

WiresharkPortable_3.4.2.paf.exe: 115181192 bytes
SHA256(WiresharkPortable_3.4.2.paf.exe)=9d9f5aba58daa4796d805bd5521f550258e57784ed9c96a6bbc39d56b0003260
RIPEMD160(WiresharkPortable_3.4.2.paf.exe)=916c0fb9692effada56074494ea9b2bb6715406b
SHA1(WiresharkPortable_3.4.2.paf.exe)=76546ae72ed6110cc32944670ae4ffd1cf1e6829

Wireshark 3.4.2 Intel 64.dmg: 130932181 bytes
SHA256(Wireshark 3.4.2 Intel 64.dmg)=2a1b79412c656e8c8efaf54d6adbc71bc8d8e7f6847fa614ada1f11395a6bad1
RIPEMD160(Wireshark 3.4.2 Intel 64.dmg)=d7b8a4907db2831624981de09d83a98a5dd44e3c
SHA1(Wireshark 3.4.2 Intel 64.dmg)=bffdade26a0504917184eb346e39b13990046427

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