[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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


 What is Wireshark?

  Wireshark is the world’s most popular network protocol analyzer. It is
  used for troubleshooting, analysis, development and education.

  Wireshark is hosted by the Wireshark Foundation, a nonprofit which
  promotes protocol analysis education. Wireshark and the foundation
  depend on your contributions in order to do their work. If you or your
  organization would like to contribute or become a sponsor, please
  visit wiresharkfoundation.org[1].

 What’s New

  Bug Fixes

   If you are upgrading Wireshark 4.2.0 or 4.2.1 on Windows you will
   need to download and install[2] Wireshark 4.2.6 or later by hand.

   A regression in the TCP Stream Graph "Time Sequence (tcptrace)"
   receive window line behavior introduced in 4.2.5 and 4.0.15 has been
   fixed. Issue 19846[3]

   The following vulnerability has been fixed:

     • wnpa-sec-2024-10[4] SPRT dissector crash. Issue 19559[5].

   The following bugs have been fixed:

     • RADIUS dissector’s dictionary loading broken in many ways. Issue
       6466[6].

     • 3.4 → 3.6.5 ASCII display is broken on CentOS 7. Issue 18096[7].

     • Funnel/Lua: Closing child window disconnects buttons of parent.
       Issue 18386[8].

     • Lua detection fails with Alpine Linux: missing: LUA_LIBRARIES.
       Issue 19841[9].

     • vnd.3gpp.5gnas payloads of type SMS not decoded inside HTTP2 5GC.
       Issue 19845[10].

     • TCP Stream Graphs green sliding window line not displayed
       correctly. Issue 19846[11].

     • Wireshark window doesn’t fully fit on screen on small resolutions
       and can’t be resized properly on Russian language. Issue
       19861[12].

     • Wireshark started from command line doesn’t set
       gui.fileopen_remembered_dir correctly on Windows. Issue
       19891[13].

     • Wireshark expects wrong length for DHCP Relay Agent Information
       Source Port Suboption. Issue 19909[14].

     • SIP P-Access-Network-Info header not correctly decoded. Issue
       19917[15].

  New and Updated Features

   There are no new or updated features in this release.

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   DHCP, E.212, MySQL, NAS-5GS, PKT CCC, ProtoBuf, RADIUS, RLC-LTE, RTP,
   SIP, SPRT, Thrift, and Wi-SUN

  New and Updated Capture File Support

   log3gpp

  Updated File Format Decoding Support

   There is no updated file format support in this release.

 Prior Versions

  This document only describes the changes introduced in Wireshark
  4.2.6. You can find release notes for prior versions at the following
  locations:

    • Wireshark 4.2.5[16]

    • Wireshark 4.2.4[17]

    • Wireshark 4.2.3[18]

    • Wireshark 4.2.2[19]

    • Wireshark 4.2.1[20]

    • Wireshark 4.2.0[21]

 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[22] 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[23] 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[24].

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

  You can learn protocol analysis and meet Wireshark’s developers at
  SharkFest[26].

 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[27].

 Frequently Asked Questions

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

 References

   1. https://wiresharkfoundation.org
   2. https://www.wireshark.org/download.html
   3. https://gitlab.com/wireshark/wireshark/-/issues/19846
   4. https://www.wireshark.org/security/wnpa-sec-2024-10
   5. https://gitlab.com/wireshark/wireshark/-/issues/19559
   6. https://gitlab.com/wireshark/wireshark/-/issues/6466
   7. https://gitlab.com/wireshark/wireshark/-/issues/18096
   8. https://gitlab.com/wireshark/wireshark/-/issues/18386
   9. https://gitlab.com/wireshark/wireshark/-/issues/19841
  10. https://gitlab.com/wireshark/wireshark/-/issues/19845
  11. https://gitlab.com/wireshark/wireshark/-/issues/19846
  12. https://gitlab.com/wireshark/wireshark/-/issues/19861
  13. https://gitlab.com/wireshark/wireshark/-/issues/19891
  14. https://gitlab.com/wireshark/wireshark/-/issues/19909
  15. https://gitlab.com/wireshark/wireshark/-/issues/19917
  16. https://www.wireshark.org/docs/relnotes/wireshark-4.2.5.html
  17. https://www.wireshark.org/docs/relnotes/wireshark-4.2.4.html
  18. https://www.wireshark.org/docs/relnotes/wireshark-4.2.3.html
  19. https://www.wireshark.org/docs/relnotes/wireshark-4.2.2.html
  20. https://www.wireshark.org/docs/relnotes/wireshark-4.2.1.html
  21. https://www.wireshark.org/docs/relnotes/wireshark-4.2.0.html
  22. https://www.wireshark.org/download.html
  23. https://ask.wireshark.org/
  24. https://www.wireshark.org/lists/
  25. https://gitlab.com/wireshark/wireshark/-/issues
  26. https://sharkfest.wireshark.org
  27. https://wiresharkfoundation.org
  28. https://www.wireshark.org/faq.html


Digests

wireshark-4.2.6.tar.xz: 45015272 bytes
SHA256(wireshark-4.2.6.tar.xz)=5ec6028df29068d889c98489bf194a884b00831106fea1e921fea3c65f2003f5
SHA1(wireshark-4.2.6.tar.xz)=db0374dce360b99d8abb9a3f3471f3fc98d6d099

Wireshark-4.2.6-arm64.exe: 67985184 bytes
SHA256(Wireshark-4.2.6-arm64.exe)=602b5b95249f8955c5a6dbc41b2012c3b06a26daafbb07ed5ea66fa43c7a6574
SHA1(Wireshark-4.2.6-arm64.exe)=4ee9ec6fc05a0d63f0f3d7110964689ab9f4f122

Wireshark-4.2.6-x64.exe: 86491216 bytes
SHA256(Wireshark-4.2.6-x64.exe)=ba679117304718a009092a5327abfdbc559031d9216512fc7540cb03d30a5545
SHA1(Wireshark-4.2.6-x64.exe)=129df64c8aa44d9ce2ad191fa783faffd71301ae

Wireshark-4.2.6-x64.msi: 62926848 bytes
SHA256(Wireshark-4.2.6-x64.msi)=cf8399afd61f2cadefd73b46dc9a206186502d30f6867457fe163a94574c1214
SHA1(Wireshark-4.2.6-x64.msi)=825e5d80806f2e613373255c1e3fd3d6d280e9f6

WiresharkPortable64_4.2.6.paf.exe: 53648680 bytes
SHA256(WiresharkPortable64_4.2.6.paf.exe)=5924198bbbcd75f8f4709799b5185be1a5c20f08f678534ed00675842bcbc5d9
SHA1(WiresharkPortable64_4.2.6.paf.exe)=dde23431f3878cafa6fb5f43e461259960b4f990

Wireshark 4.2.6 Arm 64.dmg: 65590940 bytes
SHA256(Wireshark 4.2.6 Arm 64.dmg)=11fc3f8b12b8369398e373058f9b8f0730e3228611ecf3d7ecc63c5f1855241e
SHA1(Wireshark 4.2.6 Arm 64.dmg)=57ef4f0600644c15566a9b6e9e2e71a1d2735b66

Wireshark 4.2.6 Intel 64.dmg: 69344904 bytes
SHA256(Wireshark 4.2.6 Intel 64.dmg)=41601877fa5294ec7c20f8d81c799612c6bca7fa689f237fdbf6595b5fc22071
SHA1(Wireshark 4.2.6 Intel 64.dmg)=391319afa4bd74af89baf3d73d820ab0171da0ac

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.asc
Description: OpenPGP digital signature