Wireshark-announce: [Wireshark-announce] Wireshark 3.2.12 is now available
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <[email protected]>
Date: Wed, 10 Mar 2021 12:11:20 -0800
I'm proud to announce the release of Wireshark 3.2.12.


 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-03[1] Wireshark could open unsafe URLs. Issue
       17232[2]. CVE-2021-22191[3].

   The following bugs have been fixed:

     • _ws.expert columns not populated for IPv4 Issue 17228[4].

     • Buildbot crash output: fuzz-2021-02-12-1651908.pcap Issue
       17233[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

   ARP, Frame Relay, GQUIC, and NVMe Fabrics RDMA

  New and Updated Capture File Support

   iSeries

 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-03-10 18:06:44 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2021-03
   2. https://gitlab.com/wireshark/wireshark/-/issues/17232
   3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22191
   4. https://gitlab.com/wireshark/wireshark/-/issues/17228
   5. https://gitlab.com/wireshark/wireshark/-/issues/17233
   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.12.tar.xz: 31506536 bytes
SHA256(wireshark-3.2.12.tar.xz)=f6f77ecb73b59a3f6142b591d7a3e9d340ca745cbea84bf655e69c6c55b6b04e
RIPEMD160(wireshark-3.2.12.tar.xz)=5d4ac7f15b21742d10604101ffe59a012dabd0fa
SHA1(wireshark-3.2.12.tar.xz)=3d059990e31e1b99622c946bd662a0a07375144e

Wireshark-win32-3.2.12.exe: 54917112 bytes
SHA256(Wireshark-win32-3.2.12.exe)=dce6736b2b6c1e579b4d8971a8e2ef5157e90b25ec0efdd8b8362d87ee378e77
RIPEMD160(Wireshark-win32-3.2.12.exe)=21d7a970f93834dee13aab5c23dd05aaf3d1e17e
SHA1(Wireshark-win32-3.2.12.exe)=2274dffcb9115935e39952d5eae03dadbd8b41a2

Wireshark-win64-3.2.12.exe: 60069248 bytes
SHA256(Wireshark-win64-3.2.12.exe)=932cfdcf3e34451cf5f325b5aff9bcd9e94f21b1968c81adf4c96a7b0256f323
RIPEMD160(Wireshark-win64-3.2.12.exe)=169cdd341f612ff79c7e9f5c66b8be4aadd523bb
SHA1(Wireshark-win64-3.2.12.exe)=b6e86119010c0ceb4cfde12e4a21e3d2e88c3157

Wireshark-win64-3.2.12.msi: 48418816 bytes
SHA256(Wireshark-win64-3.2.12.msi)=381e2e1c90fadbc74d86a5e3e8180c293606a4c0c3c88e701ffe1e33498f8d4b
RIPEMD160(Wireshark-win64-3.2.12.msi)=c5784cb2fbbbf475ec224c0b11bdc45c1a825c85
SHA1(Wireshark-win64-3.2.12.msi)=13495b318243f5e78964137b0579e9e701ceb86a

Wireshark-win32-3.2.12.msi: 43167744 bytes
SHA256(Wireshark-win32-3.2.12.msi)=8a6582d97147754a23769757f81681e314a77e65050be0482f471fdd8fc3e46b
RIPEMD160(Wireshark-win32-3.2.12.msi)=e876f778ee91683e0ba7694d9fed9b7e35419ef4
SHA1(Wireshark-win32-3.2.12.msi)=9f49d4c46c4e19dddcf192681da184f63d5f1452

WiresharkPortable_3.2.12.paf.exe: 36769848 bytes
SHA256(WiresharkPortable_3.2.12.paf.exe)=ffeffdc3f894b4eb4dcc0ae7d169f3ea24a43ed76a245eb97acb4fb6a53098ac
RIPEMD160(WiresharkPortable_3.2.12.paf.exe)=c5bedb777232af508ac88b086d1e8da0d265cac3
SHA1(WiresharkPortable_3.2.12.paf.exe)=d5cb5e081a295fb2db6835c0e726d88e9ea91458

Wireshark 3.2.12 Intel 64.dmg: 100395537 bytes
SHA256(Wireshark 3.2.12 Intel 64.dmg)=f65f7a1afbbcdc3dcea6f2f2d8da78f1a4d0c05c3968760997221216631b63e4
RIPEMD160(Wireshark 3.2.12 Intel 64.dmg)=9dd66c329839cb5278e689a1303617a3cb645881
SHA1(Wireshark 3.2.12 Intel 64.dmg)=f617439b0e36aa41153d15cdd4db4d3655f267cc

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