Wireshark-announce: [Wireshark-announce] Wireshark 3.2.15 is now available

Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Wed, 14 Jul 2021 12:52:29 -0700
I'm proud to announce the release of Wireshark 3.2.15.


 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:

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

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

  New and Updated Features

   There are no new features in this release.

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   DNP, GTPv2, IEEE 802.11 Radio, NAN, NR RRC, OSPF, pcapng, PNIO, RSL,
   and Snort config

  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[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 2021-07-14 17:04:27 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/17419
   5. https://gitlab.com/wireshark/wireshark/-/issues/17431
   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.2.15.tar.xz: 31528636 bytes
SHA256(wireshark-3.2.15.tar.xz)=32f6cfd67b00903a1bfca02ecc4ccf72db6b70d4fda33e4a099fefb03e849bdb
RIPEMD160(wireshark-3.2.15.tar.xz)=d1e0c38cdd189416d2e713bea168726380aa84fa
SHA1(wireshark-3.2.15.tar.xz)=a3ef5ee30baa27ca0c141d9b3cd1f489a42981fd

Wireshark-win64-3.2.15.exe: 70449712 bytes
SHA256(Wireshark-win64-3.2.15.exe)=10cda1737f2f26ec6cc46670f3e45f7e42e4e5557bc2c87706fe554a97fb98e9
RIPEMD160(Wireshark-win64-3.2.15.exe)=73a560176afeeef4436c633bc6dd701b5d01681b
SHA1(Wireshark-win64-3.2.15.exe)=e1922ed12c1b7ec01e3d4c2c78ea75ca0a92614f

Wireshark-win32-3.2.15.exe: 54379192 bytes
SHA256(Wireshark-win32-3.2.15.exe)=704f7ad432e4f476e97dbd1fecb9cfa119047089d6355e8da7fdc46e8880fa3c
RIPEMD160(Wireshark-win32-3.2.15.exe)=d6eb75cdf90deb9811371087ae8efb4f60bdf1b3
SHA1(Wireshark-win32-3.2.15.exe)=2f4bbed5d8102a96714075fe0f52a3b1a39063ee

Wireshark-win64-3.2.15.msi: 48021504 bytes
SHA256(Wireshark-win64-3.2.15.msi)=0edfc1d61429f140dce2ff152ab026e84d58ab844151cf3f2ad2ca2d77a73bf0
RIPEMD160(Wireshark-win64-3.2.15.msi)=00bcfc510689d9eedcbba83c15cffb1c699519cf
SHA1(Wireshark-win64-3.2.15.msi)=20828b81195fb89c6b884c68914e15754522d366

Wireshark-win32-3.2.15.msi: 42749952 bytes
SHA256(Wireshark-win32-3.2.15.msi)=787e524512b44859bfb1c018f8c20b0b6d3c2b2e03d390727a6aa95f0b5e83ab
RIPEMD160(Wireshark-win32-3.2.15.msi)=f5e80aa4f9f44141e52c0d2f9e7bc423c1ac8b56
SHA1(Wireshark-win32-3.2.15.msi)=ef68fc9baad7eab6ef124f5cca2a006d1986d4e1

WiresharkPortable_3.2.15.paf.exe: 37171192 bytes
SHA256(WiresharkPortable_3.2.15.paf.exe)=c158b62c0ffde26ed35f9855d35e9b7516097520fec093c3b3f6364878e3a280
RIPEMD160(WiresharkPortable_3.2.15.paf.exe)=b121fbf7e01ab8488658a4e1ec6a61621df7cedc
SHA1(WiresharkPortable_3.2.15.paf.exe)=92ba8a0eaece428b02411d13da6ffaad743b5df7

Wireshark 3.2.15 Intel 64.dmg: 100432441 bytes
SHA256(Wireshark 3.2.15 Intel 64.dmg)=9a4d28d81e64884a039c08e0d6ff5e3181be45f85f7b62f370418ec554bd5ece
RIPEMD160(Wireshark 3.2.15 Intel 64.dmg)=ed340f8fd3a528f61487efa1d5d016036d23ace8
SHA1(Wireshark 3.2.15 Intel 64.dmg)=f4868631a0258605b0141d23b3580fa32b9e658f

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