Wireshark · Wireshark-announce: [Wireshark-announce] Wireshark 3.2.13 is now available

[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.2.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 vulnerabilities have been fixed:

     • wnpa-sec-2021-04[1] MS-WSP dissector excessive memory
       consumption. Issue 17331[2].

   The following bugs have been fixed:

     • TShark does not print GeoIP information Issue 14691[3].

     • Lua TvbRanges do not support truncated captures where
       tvb_captured_length < tvb_reported_length Issue 15655[4].

     • TShark error when piping to "head" Issue 16192[5].

     • Buildbot crash output: fuzz-2021-02-22-1012761.pcap Issue
       17254[6].

     • DNS IXFR/AXFR multiple response Issue 17293[7].

     • File too large Issue 17301[8].

     • Build fails with CMake 3.20 Issue 17314[9].

  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

   DECT, DNS, LDAP, MS-WSP, PROFINET, and Sysdig

  New and Updated Capture File Support

   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[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’s Q&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 2021-04-21 17:07:30 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2021-04
   2. https://gitlab.com/wireshark/wireshark/-/issues/17331
   3. https://gitlab.com/wireshark/wireshark/-/issues/14691
   4. https://gitlab.com/wireshark/wireshark/-/issues/15655
   5. https://gitlab.com/wireshark/wireshark/-/issues/16192
   6. https://gitlab.com/wireshark/wireshark/-/issues/17254
   7. https://gitlab.com/wireshark/wireshark/-/issues/17293
   8. https://gitlab.com/wireshark/wireshark/-/issues/17301
   9. https://gitlab.com/wireshark/wireshark/-/issues/17314
  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.2.13.tar.xz: 31518512 bytes
SHA256(wireshark-3.2.13.tar.xz)=d4dbd2e219016bdb6e50b4ab58070410303e4314dc2f0f886987e096e2f29360
RIPEMD160(wireshark-3.2.13.tar.xz)=7eb5f7e5fe3a516c01e054de38cec6b69c730a1f
SHA1(wireshark-3.2.13.tar.xz)=444a0ca6748b8b2c1765bb369b274740c3f04516

Wireshark-win64-3.2.13.exe: 60088296 bytes
SHA256(Wireshark-win64-3.2.13.exe)=50be4a5e3e2818c069222acc8790ad2ef99889da75b15be14de75166169cfa61
RIPEMD160(Wireshark-win64-3.2.13.exe)=5e8160d8140e130aa40b0bb5608599cc9d904a92
SHA1(Wireshark-win64-3.2.13.exe)=436417d7ff83d3e67628e6db9b0787e37ac02907

Wireshark-win32-3.2.13.exe: 54922032 bytes
SHA256(Wireshark-win32-3.2.13.exe)=cfa2c9cabd75456920902300c2f9e099a06f94bd6912cacc5571de6761f89ebf
RIPEMD160(Wireshark-win32-3.2.13.exe)=fa74c07e6fb48daad7a6cc463615ff148ec92144
SHA1(Wireshark-win32-3.2.13.exe)=cb50b0c930a49ccfecd973be12c842d60d9d3f8e

Wireshark-win32-3.2.13.msi: 43175936 bytes
SHA256(Wireshark-win32-3.2.13.msi)=92bb0382a031cddc4cda5eb9136cb5098b22041881930ee97341102e9e64bd07
RIPEMD160(Wireshark-win32-3.2.13.msi)=1e100ca727a8144c46075088a56cb437a7b2c0ba
SHA1(Wireshark-win32-3.2.13.msi)=fb3faa856ccd5f1556b5aa77d29ad5f8863f9a7a

Wireshark-win64-3.2.13.msi: 48435200 bytes
SHA256(Wireshark-win64-3.2.13.msi)=ec71d09407be230a256467e050c5750b66e03d3346fb566962af35d5f5953fd4
RIPEMD160(Wireshark-win64-3.2.13.msi)=3a3458db47be2565d5e8c79fcd445c9c5d70e7e6
SHA1(Wireshark-win64-3.2.13.msi)=44519fd6a480209062a289b3cbaa04492677fb92

WiresharkPortable_3.2.13.paf.exe: 36768056 bytes
SHA256(WiresharkPortable_3.2.13.paf.exe)=d3bb23031177bf578b821079529f9846c1458bf7bb00c6a5a48eef8b2b6c3cf7
RIPEMD160(WiresharkPortable_3.2.13.paf.exe)=9763066c1ac514b4f2fb00b3156f9324954af650
SHA1(WiresharkPortable_3.2.13.paf.exe)=3d07b7cd83f99e7e2f77c36722ae9af0642f963e

Wireshark 3.2.13 Intel 64.dmg: 100448166 bytes
SHA256(Wireshark 3.2.13 Intel 64.dmg)=f458443bb273c1b65bca1ba4e7863152ec06d0a7f9c10ff853df843135db17f8
RIPEMD160(Wireshark 3.2.13 Intel 64.dmg)=c401a668a28c42d69ce760bc7604f1f74a038465
SHA1(Wireshark 3.2.13 Intel 64.dmg)=bf1865f245ecf2971aeb608f4f5c57bdcee664f0

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