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

[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.2.16.


 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:

     • Dissector bug reported for Bluetooth Cycling Power Measurement
       characteristic for extreme angles value Issue 17505[1].

     • Raknet Addresses are incorrectly identified. Issue 17509[2].

  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

   BT ATT, DLM3, and RakNet

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

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

 Frequently Asked Questions

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

  Last updated 2021-08-24 01:34:58 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17505
   2. https://gitlab.com/wireshark/wireshark/-/issues/17509
   3. https://www.wireshark.org/download.html#thirdparty
   4. https://ask.wireshark.org/
   5. https://www.wireshark.org/lists/
   6. https://gitlab.com/wireshark/wireshark/-/issues
   7. https://www.wireshark.org/faq.html


Digests

wireshark-3.2.16.tar.xz: 31530096 bytes
SHA256(wireshark-3.2.16.tar.xz)=236068cebbb0de99eebf9ed5a942bfa3342683ea91865f6f76c6111cffc81764
RIPEMD160(wireshark-3.2.16.tar.xz)=f7bd09c3214fb8da0df5bf1f8fd67f0900925269
SHA1(wireshark-3.2.16.tar.xz)=a53f42a002215c50c58110a8f411f8714652d853

Wireshark-win64-3.2.16.exe: 70455824 bytes
SHA256(Wireshark-win64-3.2.16.exe)=d83ff59b6cff5deecf63a940a2bce6a3b2ce5dd108b10da480b3b98e1f040e3e
RIPEMD160(Wireshark-win64-3.2.16.exe)=24772871497e33f945c5b24bbcf624d44d721d92
SHA1(Wireshark-win64-3.2.16.exe)=f3393c0702d7cf4eb8b1ab15e9c3679dbcdfdf74

Wireshark-win32-3.2.16.exe: 54385968 bytes
SHA256(Wireshark-win32-3.2.16.exe)=9dc82a9f26d7793bda02739f59ae7b9b27f15e3a03cac7517134127e520f932f
RIPEMD160(Wireshark-win32-3.2.16.exe)=4708eddb29949c499cbf0a033b5dbcd1e9418f15
SHA1(Wireshark-win32-3.2.16.exe)=cfde57212e07a6c5f3fb91fd2408b8c7d282d4e4

Wireshark-win64-3.2.16.msi: 48041984 bytes
SHA256(Wireshark-win64-3.2.16.msi)=2ef00d2b097a001bc77e3854731ca72dde5657289b262e8f809e049f46047344
RIPEMD160(Wireshark-win64-3.2.16.msi)=6bdd6955fb96b39096aef8dd02640f968263f761
SHA1(Wireshark-win64-3.2.16.msi)=d3111de0dc3c9a8e05d615e5220d815b30e6bf17

Wireshark-win32-3.2.16.msi: 42754048 bytes
SHA256(Wireshark-win32-3.2.16.msi)=5c7b3975ca8bbaa6f6163ef7c3066b592fa4f3cc946b712d6eb2e7d56ddedbc1
RIPEMD160(Wireshark-win32-3.2.16.msi)=9266b12dd24f5c53114d2c876d435e1a6b94bc93
SHA1(Wireshark-win32-3.2.16.msi)=8ddd29f179e16c601716f9664320a673c1b1acd0

WiresharkPortable_3.2.16.paf.exe: 37188656 bytes
SHA256(WiresharkPortable_3.2.16.paf.exe)=527961cbec9b595a853d24620adbf5529b0cfef30a3bdb1aa459880120753088
RIPEMD160(WiresharkPortable_3.2.16.paf.exe)=8a32af4b7078f12d321af91edab84d16073dee45
SHA1(WiresharkPortable_3.2.16.paf.exe)=72ff03ae268a303c540b2133d51ff55da3e4ee26

Wireshark 3.2.16 Intel 64.dmg: 100446331 bytes
SHA256(Wireshark 3.2.16 Intel 64.dmg)=9821fe733ffbc277047bcda3f36ef312da0df853eeeb64a369ecfeacf69bf469
RIPEMD160(Wireshark 3.2.16 Intel 64.dmg)=1787e47a43be10d80db1a0c21419756e7adb1a7b
SHA1(Wireshark 3.2.16 Intel 64.dmg)=3f35ab967c9c84d5598190c2d198b0c94aeae199

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