[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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

  We do not ship official 32-bit Windows packages for Wireshark 4.0 and
  later. If you need to use Wireshark on that platform, we recommend
  using the latest 3.6 release. Issue 17779[1]

  If you’re running Wireshark on macOS and upgraded to macOS 13 from an
  earlier version, you might have to open and run the “Uninstall
  ChmodBPF” package, then open and run “Install ChmodBPF” in order to
  reset the ChmodBPF Launch Daemon. Issue 18734[2].

  Bug Fixes

   The following bugs have been fixed:

     • Error loading g729.so plugin with Wireshark 4.0.9 and 3.6.17 on
       macOS. Issue 19374[3].

  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

   There are no updated protocols in this release.

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

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

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

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

 Frequently Asked Questions

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

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/17779
   2. https://gitlab.com/wireshark/wireshark/-/issues/18734
   3. https://gitlab.com/wireshark/wireshark/-/issues/19374
   4. https://www.wireshark.org/download.html
   5. https://ask.wireshark.org/
   6. https://www.wireshark.org/lists/
   7. https://gitlab.com/wireshark/wireshark/-/issues
   8. https://sharkfest.wireshark.org
   9. https://wiresharkfoundation.org
  10. https://www.wireshark.org/faq.html


Digests

wireshark-4.0.10.tar.xz: 43124192 bytes
SHA256(wireshark-4.0.10.tar.xz)=b2e3ff03fa2be9058a9ffbedd12b0a670433bd16c8cc6c432ab48dabc2df1898
SHA1(wireshark-4.0.10.tar.xz)=830ba7ff602da90323bbc5ec15941c0878d9ee4a

Wireshark-win64-4.0.10.exe: 79141976 bytes
SHA256(Wireshark-win64-4.0.10.exe)=085d9aa4f6614730f132fb5c28ec5fa445dea79687e4c648d586de569ffcc5e2
SHA1(Wireshark-win64-4.0.10.exe)=1e5ea0f5fa1a8835bcfc9587efa4bf58c495d13f

Wireshark-win64-4.0.10.msi: 53219328 bytes
SHA256(Wireshark-win64-4.0.10.msi)=965e532c05c4be1423e72bcb6c3350aca3f64b42543807c1193705ab7a1e59af
SHA1(Wireshark-win64-4.0.10.msi)=b6e13884d0a6ab5f41e92a127d85261fc71b28c4

WiresharkPortable64_4.0.10.paf.exe: 45802800 bytes
SHA256(WiresharkPortable64_4.0.10.paf.exe)=40e4da853067905cee3447d64b3399d8101b90265bcc213081b750e33f78bb8f
SHA1(WiresharkPortable64_4.0.10.paf.exe)=15a0ba51e056029699484a13adb4c52bd30703a9

Wireshark 4.0.10 Arm 64.dmg: 63446426 bytes
SHA256(Wireshark 4.0.10 Arm 64.dmg)=178201c6b010e8ee7058a640b2592a8759a8ffa323f5a04434273a3501530a94
SHA1(Wireshark 4.0.10 Arm 64.dmg)=0ec52abbd32c97a0f1ee21b590f6dc919960c7b2

Wireshark 4.0.10 Intel 64.dmg: 66986608 bytes
SHA256(Wireshark 4.0.10 Intel 64.dmg)=f0ae6cfc2ecf1e7f5b1475c91bb2c5f7ac63174405a667056bb29b8c17f1180b
SHA1(Wireshark 4.0.10 Intel 64.dmg)=926abb7a6bdb0f58b6b4b6aaba19353207d90ce6

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