Wireshark-announce: [Wireshark-announce] Wireshark 3.2.10 is now available
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <[email protected]>
Date: Fri, 18 Dec 2020 13:38:52 -0800
I'm proud to announce the release of Wireshark 3.2.10.


 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:

     • macos-setup.sh can’t find SDK on macOS Big Sur, as it went to 11
       Bug 17043[1].

     • Wireshark 3.4.1 hangs on startup on macOS Big Sur 11.0.1 Bug
       17075[2].

     • False expect error seen on FCoE frames (not seen with older
       release wireshark 1.2.18) Bug 17084[3].

     • Several libraries missing in 3.4.1 and 3.2.9 installers for macOS
       Bug 17086[4].

  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

   FC-dNS, FCoE, and SNMP

  New and Updated Capture File Support

   There is no new or updated capture file support in this release.

 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[5] 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[6] 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[7].

  Issues and feature requests can be reported on the issue tracker[8].

 Frequently Asked Questions

  A complete FAQ is available on the Wireshark web site[9].

  Last updated 2020-12-18 18:22:35 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17043
   2. https://gitlab.com/wireshark/wireshark/-/issues/17075
   3. https://gitlab.com/wireshark/wireshark/-/issues/17084
   4. https://gitlab.com/wireshark/wireshark/-/issues/17086
   5. https://www.wireshark.org/download.html#thirdparty
   6. https://ask.wireshark.org/
   7. https://www.wireshark.org/lists/
   8. https://gitlab.com/wireshark/wireshark/-/issues
   9. https://www.wireshark.org/faq.html


Digests

wireshark-3.2.10.tar.xz: 31669004 bytes
SHA256(wireshark-3.2.10.tar.xz)=1e9e239f2449f240a7910ed598084ccaf8ea308b2b46b196c5adbec59612226c
RIPEMD160(wireshark-3.2.10.tar.xz)=015fc447352e34c35c9f2042e2809563dcc5e795
SHA1(wireshark-3.2.10.tar.xz)=691bd151d0d5e7a23b73e7972490947c0af9cf1d

Wireshark-win32-3.2.10.exe: 54916512 bytes
SHA256(Wireshark-win32-3.2.10.exe)=9f72871bea7ea2b62f5c7d1e62f16e9dead68c6ffe457dc04b4e1ccbe77ad155
RIPEMD160(Wireshark-win32-3.2.10.exe)=f9b668740c83ff6b645f58e869c18a27b352a2ea
SHA1(Wireshark-win32-3.2.10.exe)=678a901733b364bc73f060e27998edc7f9bafac9

Wireshark-win64-3.2.10.exe: 60074584 bytes
SHA256(Wireshark-win64-3.2.10.exe)=e33e27f51910e156b46f953e0fc8c336a99e54e0c175deea03b129706db7528b
RIPEMD160(Wireshark-win64-3.2.10.exe)=489dac6045dbb019463ef5e551d012e8e1a1bcdc
SHA1(Wireshark-win64-3.2.10.exe)=db937e4764cd252f6a03d68f9fa2770ea53e614a

Wireshark-win32-3.2.10.msi: 43171840 bytes
SHA256(Wireshark-win32-3.2.10.msi)=7749977298f212312c9714356fcaedc57d66b5eac63fdab93906831867887303
RIPEMD160(Wireshark-win32-3.2.10.msi)=a0bc867143a04640a955fa610c83f96635af45f6
SHA1(Wireshark-win32-3.2.10.msi)=f14553785319f1e9a8dde15dd865d4a49fc62e5d

Wireshark-win64-3.2.10.msi: 48410624 bytes
SHA256(Wireshark-win64-3.2.10.msi)=44d8753dae0f66006d17e826927008cc1a92ff78fe76b4a48ed6467c66d2fc44
RIPEMD160(Wireshark-win64-3.2.10.msi)=dc8f2d193e6c0b0e4723a888270557ab2e5b176a
SHA1(Wireshark-win64-3.2.10.msi)=95f95c128471b119d4b5c1799f01f76ef2eb2280

WiresharkPortable_3.2.10.paf.exe: 36753200 bytes
SHA256(WiresharkPortable_3.2.10.paf.exe)=c763dd9c019a19a55dcecab55f1071a8b0cfea5ef4a6e5b5ee6a3158c0021c54
RIPEMD160(WiresharkPortable_3.2.10.paf.exe)=38479bb8fe5dfde9bbe3dddde159e663ee9e60bf
SHA1(WiresharkPortable_3.2.10.paf.exe)=309e471cf434f49f71db1e250e41b18e705d7146

Wireshark 3.2.10 Intel 64.dmg: 100352511 bytes
SHA256(Wireshark 3.2.10 Intel 64.dmg)=481bc21bed4572ff6c840e54cb90810ac17f12ffc14095b80c2344184240e097
RIPEMD160(Wireshark 3.2.10 Intel 64.dmg)=bb32756fd9ee497ad52c5b7c9d00fdbd512c0ad7
SHA1(Wireshark 3.2.10 Intel 64.dmg)=f4eab92c14b0142bb6e37a962b4ef5a131a9213e

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