[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.6.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

  This is the last release branch with support for 32-bit Windows.
  Updates will no longer be available after May 22, 2024 for that
  platform. Issue 17779[1]

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2023-08[2] ISO 15765 and ISO 10681 dissector crash.
       Issue 18839[3].

   The following bugs have been fixed:

     • UTF-8 characters end up escaped in PSML output Issue 10445[4].

     • Export filtered displayed packets won’t save IP fragments of SCTP
       fragments needed to reassemble a displayed frame. Issue 12597[5].

     • The intelligent scroll bar or minimap is not predictable on
       locating and scrolling Issue 13989[6].

     • If you mark (or unmark) the currently-selected frame, the packet
       details still say it’s not marked (or it is marked) Issue
       14330[7].

     • Sorting Packet Loss Column is not sorting correct Issue 16785[8].

     • SIP TCP decoding regression from Wireshark 1.99.0 to 3.6.8 Issue
       18411[9].

     • ChmodBPF not working on macOS Ventura 13.1 Issue 18734[10].

     • Symbolic links to packages in macOS dmg can’t be double-clicked
       to install on macOS 13.2 Issue 18830[11].

     • Potential memory leak in tshark.c Issue 18837[12].

     • Fuzz job crash output: fuzz-2023-02-05-7303.pcap Issue 18842[13].

     • f5fileinfo: Hardware platforms missing descriptions Issue
       18848[14].

     • The lines in the intelligent scrollbar are off by one Issue
       18850[15].

     • TECMP dissector shows the wrong Voltage in Vendor Data Issue
       18871[16].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   DHCP, ERF, F5 Ethernet trailer, GMR-1 RR, Gryphon, GSM SMS, H.450,
   ISO 10681, ISO 15765, NAS-5GS, NR RRC, NS Trace, OptoMMP, PDCP-LTE,
   QSIG, ROHC, RSVP, RTCP, SCTP, SIP, TCP, TECMP, TWAMP, and UMTS RLC

  New and Updated Capture File Support

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

  New File Format Decoding Support

   There is no new or updated file format 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[17] 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 "Help › About
  Wireshark › Folders" or `tshark -G 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[18] 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[19].

  Bugs and feature requests can be reported on the issue tracker[20].

 How You Can Help

  The Wireshark Foundation helps as many people as possible understand
  their networks as much as possible. You can find out more and donate
  at wiresharkfoundation.org[21].

 Frequently Asked Questions

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

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17779
   2. https://www.wireshark.org/security/wnpa-sec-2023-08
   3. https://gitlab.com/wireshark/wireshark/-/issues/18839
   4. https://gitlab.com/wireshark/wireshark/-/issues/10445
   5. https://gitlab.com/wireshark/wireshark/-/issues/12597
   6. https://gitlab.com/wireshark/wireshark/-/issues/13989
   7. https://gitlab.com/wireshark/wireshark/-/issues/14330
   8. https://gitlab.com/wireshark/wireshark/-/issues/16785
   9. https://gitlab.com/wireshark/wireshark/-/issues/18411
  10. https://gitlab.com/wireshark/wireshark/-/issues/18734
  11. https://gitlab.com/wireshark/wireshark/-/issues/18830
  12. https://gitlab.com/wireshark/wireshark/-/issues/18837
  13. https://gitlab.com/wireshark/wireshark/-/issues/18842
  14. https://gitlab.com/wireshark/wireshark/-/issues/18848
  15. https://gitlab.com/wireshark/wireshark/-/issues/18850
  16. https://gitlab.com/wireshark/wireshark/-/issues/18871
  17. https://www.wireshark.org/download.html
  18. https://ask.wireshark.org/
  19. https://www.wireshark.org/lists/
  20. https://gitlab.com/wireshark/wireshark/-/issues
  21. https://wiresharkfoundation.org
  22. https://www.wireshark.org/faq.html


Digests

wireshark-3.6.12.tar.xz: 39975988 bytes
SHA256(wireshark-3.6.12.tar.xz)=0402f40fe8b026bf64a9d9fde13d3ad4adae08c3a72ca05b2d3a60a924da7591
SHA1(wireshark-3.6.12.tar.xz)=78e578fad829fa9b4291b7bae196cf247c107284

Wireshark-win32-3.6.12.exe: 61131744 bytes
SHA256(Wireshark-win32-3.6.12.exe)=e87c3b933dd1c0692ec8c944706326cbc167738a103ebab439725a6dffafef7f
SHA1(Wireshark-win32-3.6.12.exe)=b345d81dce4f64bdfb2c1518b0378f0f57bed7e2

Wireshark-win64-3.6.12.exe: 77325248 bytes
SHA256(Wireshark-win64-3.6.12.exe)=a23284a1dd2c8914e4a98912186b21e2108470ea683f400a5eec2934c47c2b02
SHA1(Wireshark-win64-3.6.12.exe)=d2f6d56d18a0d59dbce78d9439e0d9cfc8814ccc

Wireshark-win32-3.6.12.msi: 45690880 bytes
SHA256(Wireshark-win32-3.6.12.msi)=29242cd8e93ecd3d11b37430a34fcba0586c9eb219e9d5208095939cc946d1d9
SHA1(Wireshark-win32-3.6.12.msi)=7a7f67642b9c02825d5c9027946a7230b64bf736

Wireshark-win64-3.6.12.msi: 51023872 bytes
SHA256(Wireshark-win64-3.6.12.msi)=0e9953ec97cf0dd77dec019b87df5920f05365a6cbacac2d71cff1d24592b458
SHA1(Wireshark-win64-3.6.12.msi)=5d3406786e21f14ce59ec8835ca93b01afc4d292

WiresharkPortable64_3.6.12.paf.exe: 44468600 bytes
SHA256(WiresharkPortable64_3.6.12.paf.exe)=2c707dc04d5569235b77d957a006d9f3b94872c10be5a945b4f87e2ccba37ecf
SHA1(WiresharkPortable64_3.6.12.paf.exe)=3489aa186394abae093af922c5ac7ece4fd72a02

WiresharkPortable32_3.6.12.paf.exe: 39711264 bytes
SHA256(WiresharkPortable32_3.6.12.paf.exe)=b95dbc9538262e3c01b786968483ee3187a087db9806e84cdbf0ca392dbc4bd5
SHA1(WiresharkPortable32_3.6.12.paf.exe)=3202bb1725d8fae3de884014a41a2a6ebbd3c718

Wireshark 3.6.12 Arm 64.dmg: 141860689 bytes
SHA256(Wireshark 3.6.12 Arm 64.dmg)=f2c4d000ba913e29956ea6ee5f15a357bb8161beb44ab5802aed71ae53774de8
SHA1(Wireshark 3.6.12 Arm 64.dmg)=8d3f58e3e51911620133538730c92781f11761a8

Wireshark 3.6.12 Intel 64.dmg: 142124001 bytes
SHA256(Wireshark 3.6.12 Intel 64.dmg)=b687ae4cfa3d2e0e4bdfafb6f3777de71bed8d711f7a7a8817ea3251294ad1c2
SHA1(Wireshark 3.6.12 Intel 64.dmg)=7d1c4dad3531f9ffcce39678bbed6619e6f101d0

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