[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 This is expected to be the final supported version of the 3.2 branch.

 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:

     • AMQP 0.9: dissector fails to handle Content-Body frame split
       across TCP packets Issue 14217[1].

     • Wireshark ignored some character in filename when exporting SMB
       objects. Issue 17530[2].

     • tshark -z credentials: assertion failed: (allocator→in_scope)
       Issue 17576[3].

     • IS-IS Extended IP Reachability Prefix-SID not decoded properly
       Issue 17610[4].

     • GUI freezes when clicking on large (non-capture) file in File
       chooser Issue 17620[5].

     • Crash after selecting a different profile while capturing Issue
       17622[6].

  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

   AMQP, BGP, CoAP, DCERPC SPOOLSS, GTP, InfiniBand, ISIS LSP, ISObus
   VT, JPEG, MP2T, NORDIC_BLE, QUIC, RTCP, SMB, TWAMP-Control, and VSS
   Monitoring

  New and Updated Capture File Support

   CAM Inspector, Ixia IxVeriWave, pcapng, and USBDump

 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[7] 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[8] 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[9].

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

 Frequently Asked Questions

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

  Last updated 2021-10-06 17:39:18 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/14217
   2. https://gitlab.com/wireshark/wireshark/-/issues/17530
   3. https://gitlab.com/wireshark/wireshark/-/issues/17576
   4. https://gitlab.com/wireshark/wireshark/-/issues/17610
   5. https://gitlab.com/wireshark/wireshark/-/issues/17620
   6. https://gitlab.com/wireshark/wireshark/-/issues/17622
   7. https://www.wireshark.org/download.html#thirdparty
   8. https://ask.wireshark.org/
   9. https://www.wireshark.org/lists/
  10. https://gitlab.com/wireshark/wireshark/-/issues
  11. https://www.wireshark.org/faq.html


Digests

wireshark-3.2.17.tar.xz: 31543080 bytes
SHA256(wireshark-3.2.17.tar.xz)=21cb6f0eb4eebc5d9a77e2105ce12f2196aaf26e6403d4c24274774521f5e83b
RIPEMD160(wireshark-3.2.17.tar.xz)=cc1a65b62ffa22d8a430dc9f52df31773b6d18a8
SHA1(wireshark-3.2.17.tar.xz)=c513e0184d8850808374be33e4d613d20efaa416

Wireshark-win64-3.2.17.exe: 70469024 bytes
SHA256(Wireshark-win64-3.2.17.exe)=b9b14886182b10dbd8aa580dc77ae1b914498c36da0b9fa62f84e459e7eed954
RIPEMD160(Wireshark-win64-3.2.17.exe)=6490538a60702159dc44f35948df52281be47760
SHA1(Wireshark-win64-3.2.17.exe)=5e6ec6071f7352994edfc5a643925109bd8bbd69

Wireshark-win32-3.2.17.exe: 54397016 bytes
SHA256(Wireshark-win32-3.2.17.exe)=178bc6981e156df2a7474c8a7819f2170a39afb3b14384da43d05757c70bdce1
RIPEMD160(Wireshark-win32-3.2.17.exe)=a57dac382c7487565337ee92f96033e2963d16b6
SHA1(Wireshark-win32-3.2.17.exe)=3556e59442a1e5e6f727049db6b1ed9d0b186c84

Wireshark-win64-3.2.17.msi: 48041984 bytes
SHA256(Wireshark-win64-3.2.17.msi)=50580eed9cdd78154c65c73764fe4eaa2f130a859aa87feb3b42ae3e12d1a03a
RIPEMD160(Wireshark-win64-3.2.17.msi)=6426d203b46cad83efb132e19384d103138aa710
SHA1(Wireshark-win64-3.2.17.msi)=148b0fee7789cf3ded87bcb4e19deb3a0cb1f25b

Wireshark-win32-3.2.17.msi: 42754048 bytes
SHA256(Wireshark-win32-3.2.17.msi)=6c488da6459fade36f4ad747ac4fd64dad4e0767eb70231a1e81aadfacb548d1
RIPEMD160(Wireshark-win32-3.2.17.msi)=a86b915b92ee4c2fa03e058098538ce5d8cf3c9f
SHA1(Wireshark-win32-3.2.17.msi)=f1e423657c586193d6a1b4e4cb9d2785bb708ceb

WiresharkPortable_3.2.17.paf.exe: 37193464 bytes
SHA256(WiresharkPortable_3.2.17.paf.exe)=c1b44253e615e3a2f4b7c18811663ac2962de5e55118f6e47ea8495e626b47e0
RIPEMD160(WiresharkPortable_3.2.17.paf.exe)=55b6cc292570eb3c419f85a9e6b6f636c35ca189
SHA1(WiresharkPortable_3.2.17.paf.exe)=052dcd46697ba9a3f5edd60d35d941513dce9ed7

Wireshark 3.2.17 Intel 64.dmg: 100486609 bytes
SHA256(Wireshark 3.2.17 Intel 64.dmg)=0f8b8baad6f778537636fbdd66929be919a16ae174b64745d52a186adea89bae
RIPEMD160(Wireshark 3.2.17 Intel 64.dmg)=f296d6423d71af5282e6ca2d7717669cc422e9c3
SHA1(Wireshark 3.2.17 Intel 64.dmg)=b02cee833d6f97b6e0379736a34bd17168699872

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 Arm 64.dmg"
    Other: openssl sha256 wireshark-x.y.z.tar.xz

Attachment: OpenPGP_signature
Description: OpenPGP digital signature