Wireshark-announce: [Wireshark-announce] Wireshark 3.2.11 is now available
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <[email protected]>
Date: Fri, 29 Jan 2021 11:43:39 -0800
I'm proud to announce the release of Wireshark 3.2.11.


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

     • Adding filter while "Telephony→VoIP Calls→Flow Sequence" open
       causes OOB memory reads and potential crashes. Bug 16952[1].

     • SOMEIP-SD hidden entries are off Bug 17091[2].

     • Dark mode not working in Wireshark 3.4.2 on macOS Bug 17098[3].

     • Documentation - editorial error - README.dissector bad reference
       Bug 17141[4].

     • AUTOSAR-NM: PNI TF-String wrong way around Bug 17154[5].

     • Fibre Channel parsing errors even with the fix for #17084 Bug
       17168[6].

     • Buildbot crash output: fuzz-2021-01-22-3387835.pcap Bug 17174[7].

     • Dissection error on large ZVT packets Bug 17177[8].

     • TShark crashes with -T ek option Bug 17179[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

   AUTOSAR-NM, DHCPv6, DoIP, FC ELS, SIP, SOME/IP-SD, and ZVT

  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-01-29 17:59:08 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/16952
   2. https://gitlab.com/wireshark/wireshark/-/issues/17091
   3. https://gitlab.com/wireshark/wireshark/-/issues/17098
   4. https://gitlab.com/wireshark/wireshark/-/issues/17141
   5. https://gitlab.com/wireshark/wireshark/-/issues/17154
   6. https://gitlab.com/wireshark/wireshark/-/issues/17168
   7. https://gitlab.com/wireshark/wireshark/-/issues/17174
   8. https://gitlab.com/wireshark/wireshark/-/issues/17177
   9. https://gitlab.com/wireshark/wireshark/-/issues/17179
  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.11.tar.xz: 31502732 bytes
SHA256(wireshark-3.2.11.tar.xz)=25a27bb6cd9c24c1446cd9fafc47df05af91a3668b12bde8b9164482db373c4d
RIPEMD160(wireshark-3.2.11.tar.xz)=e22219e656f77d85a61150d785f5e86310efcada
SHA1(wireshark-3.2.11.tar.xz)=bc06c22831dc0e071b9d43929f39f8d0ca7760e9

Wireshark-win64-3.2.11.exe: 60105008 bytes
SHA256(Wireshark-win64-3.2.11.exe)=6dacf11653b920dd86bd1e087d9d2fdd9e8588e019bf899bc67038aa4b2a8985
RIPEMD160(Wireshark-win64-3.2.11.exe)=54e337aeec8cc2f893d3e36b5a51bc67f05f0c4f
SHA1(Wireshark-win64-3.2.11.exe)=1a8b58eb66ba3e9d9349bc607f503d353925fa64

Wireshark-win32-3.2.11.exe: 54930832 bytes
SHA256(Wireshark-win32-3.2.11.exe)=d4bd1bf56c8b34da870aacb392749df5046fed152a35932f7a2a77db7888887d
RIPEMD160(Wireshark-win32-3.2.11.exe)=f0b983140b16e7ae87854e55288123bbc82f7bc7
SHA1(Wireshark-win32-3.2.11.exe)=b045e2a9f706373b835b5246734bbf2f6c7fb3d9

Wireshark-win64-3.2.11.msi: 48418816 bytes
SHA256(Wireshark-win64-3.2.11.msi)=8a10529bc9f4f7f547dac623a0282766338c8577d856541cb20a2e829d9b415a
RIPEMD160(Wireshark-win64-3.2.11.msi)=b412a473aa67f50c3f7f31a01445e1d8e50cbd06
SHA1(Wireshark-win64-3.2.11.msi)=da8e8621e826a2d8daead765cfcbf63131c99c35

Wireshark-win32-3.2.11.msi: 43175936 bytes
SHA256(Wireshark-win32-3.2.11.msi)=6106bc53e16da975e8a09c34778bd200cff589c9af203c913ce8bb436f309613
RIPEMD160(Wireshark-win32-3.2.11.msi)=b76d231e2bd4812792c87606e63c72a01afd8f5f
SHA1(Wireshark-win32-3.2.11.msi)=f0752328c4976d78f1b3aa74313109006f01a284

WiresharkPortable_3.2.11.paf.exe: 36764840 bytes
SHA256(WiresharkPortable_3.2.11.paf.exe)=642e63bfca5bc6075e3ac5462f22aadc50d0b4cfab14bb88fa051c9716f1aad8
RIPEMD160(WiresharkPortable_3.2.11.paf.exe)=132f68804bda193bcf3eb126566587587325fc73
SHA1(WiresharkPortable_3.2.11.paf.exe)=71e4c3630038510223f9be1d9dbc6c0aa12beeee

Wireshark 3.2.11 Intel 64.dmg: 100377734 bytes
SHA256(Wireshark 3.2.11 Intel 64.dmg)=f9d3bcd48f14dc9b178c4729da547fafb3f3f642f3260124a3fa3be7efa2add9
RIPEMD160(Wireshark 3.2.11 Intel 64.dmg)=fd4444756162f65f3157d3f8323030defed3afbc
SHA1(Wireshark 3.2.11 Intel 64.dmg)=8ae656c6c2851b31cca7d3594737cc262b5673ec

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