[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 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-2021-06[1] DNP dissector crash. Issue 17462[2].
       CVE-2021-22235[3].

   The following bugs have been fixed:

     • TCP dissector - Erroneous DSACK reporting Issue 17315[4].

     • No wlan_radio.duration calculated for PHY type: 802.11ac (VHT)
       Issue 17419[5].

     • NAN Dissector has wrong minimum length for availability attribute
       Issue 17431[6].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   ASTERIX, BT LE LL, DCE RPC, DNP, GTPv2, IEEE 802.11 Radio, LDAP, NAN,
   NORDIC_BLE, NR RRC, OSPF, pcapng, PNIO, RSL, S101, Snort config, and
   TCP

  New and Updated Capture File Support

   Catapult DCT2000, ERF, and pcap

 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-07-14 17:01:08 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2021-06
   2. https://gitlab.com/wireshark/wireshark/-/issues/17462
   3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22235
   4. https://gitlab.com/wireshark/wireshark/-/issues/17315
   5. https://gitlab.com/wireshark/wireshark/-/issues/17419
   6. https://gitlab.com/wireshark/wireshark/-/issues/17431
   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.7.tar.xz: 32311140 bytes
SHA256(wireshark-3.4.7.tar.xz)=6c4cee51ef997cb9d9aaee84113525a5629157d3c743d7c4e320000de804a09d
RIPEMD160(wireshark-3.4.7.tar.xz)=be6d3f018532d17b0154677c6fd54c61a2f289f3
SHA1(wireshark-3.4.7.tar.xz)=3fa4bb774030442b9908243a9927d38479c52bf5

Wireshark-win64-3.4.7.exe: 71354272 bytes
SHA256(Wireshark-win64-3.4.7.exe)=b61fcdb21a5a1f40d267748300d29b04562277175d827312202c6ea918065238
RIPEMD160(Wireshark-win64-3.4.7.exe)=8789c7d43d7822f83e3887a8584abc262c93f3fa
SHA1(Wireshark-win64-3.4.7.exe)=55620cf189b44e84f654d39299af106b6ea1a5f3

Wireshark-win32-3.4.7.exe: 55389856 bytes
SHA256(Wireshark-win32-3.4.7.exe)=1ff1e362aa96864e2d08e0241d6c36fc2ee2f9bb228695da5a0040e8b2ea1542
RIPEMD160(Wireshark-win32-3.4.7.exe)=a62874a0acfaf48335f8470a9fbc5adbdda68b64
SHA1(Wireshark-win32-3.4.7.exe)=f2970ef2bca028768008d687bc04a678c53c299f

Wireshark-win64-3.4.7.msi: 49106944 bytes
SHA256(Wireshark-win64-3.4.7.msi)=86dd46ede8ce640623686d73b9f1bd5f514428ea3f2d335325db4867330a9d38
RIPEMD160(Wireshark-win64-3.4.7.msi)=aba2d1f6595165bb840bd2b5e74609b010d940e9
SHA1(Wireshark-win64-3.4.7.msi)=f0a1da013a66aa8d138f05d83889df4465b06cd1

Wireshark-win32-3.4.7.msi: 43905024 bytes
SHA256(Wireshark-win32-3.4.7.msi)=d6e900c35637df916d157c1c932dd3a60b6d9e1e4d1b93795efe3208ce016d7f
RIPEMD160(Wireshark-win32-3.4.7.msi)=d0bc87c9ca19a420a367fb91dcc42cd0ab3694b9
SHA1(Wireshark-win32-3.4.7.msi)=f601e8874355c46c0bf836f6e28b48f5f166ae7d

WiresharkPortable_3.4.7.paf.exe: 38205224 bytes
SHA256(WiresharkPortable_3.4.7.paf.exe)=6529ee4f5d6d850dafaea7bbb334c7c9858e24af4a8b48a2e0f1f75204f8b20d
RIPEMD160(WiresharkPortable_3.4.7.paf.exe)=a6333431329c231aca67386840c0725957f69e9a
SHA1(WiresharkPortable_3.4.7.paf.exe)=85f4449bc1295d3a24fe750c211b1fa42724574a

Wireshark 3.4.7 Intel 64.dmg: 131023034 bytes
SHA256(Wireshark 3.4.7 Intel 64.dmg)=454c2533aed96e3a39d0c21f9edecad0d75ef9c688d3aef7619895fb7a3c5db4
RIPEMD160(Wireshark 3.4.7 Intel 64.dmg)=3dc8b43a2b9173d4e6b79c9313b28558ff957225
SHA1(Wireshark 3.4.7 Intel 64.dmg)=bce18e4357e17be18b822bd8c772bb7637268287

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