[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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


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

     • vcruntime140_1.dll deleted on Wireshark update/install Issue
       17506[2].

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

     • Editcap saving files as ethernet when specifying '-T
       ieee-802-11-*' Issue 17520[4].

     • CoAP dissector confuses Content-Format with Accept Issue
       17536[5].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   BT ATT, BT LE LL, CoAP, DLM3, GSM SIM, iLBC, 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[6] 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[7] 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[8].

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

 Frequently Asked Questions

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

  Last updated 2021-08-25 18:31:37 UTC

 References

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


Digests

wireshark-3.4.8.tar.xz: 32314976 bytes
SHA256(wireshark-3.4.8.tar.xz)=58a7fa8dfe2010a8c8b7dcf66438c653e6493d47eb936ba48ef49d4aa4dbd725
RIPEMD160(wireshark-3.4.8.tar.xz)=573fd48c88c514de5000835c849d88c7df89e39a
SHA1(wireshark-3.4.8.tar.xz)=b8ee02e6c708d74befafe48f80f294313345f90b

Wireshark-win64-3.4.8.exe: 71375600 bytes
SHA256(Wireshark-win64-3.4.8.exe)=7f65c2edb7ea53e6abce513e2dc5b4c3dc323738d49b54718255c2944c776c5a
RIPEMD160(Wireshark-win64-3.4.8.exe)=523331ca425048468f392fc568123f4d5230ec0d
SHA1(Wireshark-win64-3.4.8.exe)=0df4616b8c1fe802496642445274dd68515b50b5

Wireshark-win32-3.4.8.exe: 55415120 bytes
SHA256(Wireshark-win32-3.4.8.exe)=473e20a63a5851b7a484b3faf509f7882d8d885831a16bc448f14e6ed0932e65
RIPEMD160(Wireshark-win32-3.4.8.exe)=fbb198f89daf563f63cc5109f2b77b7b86397226
SHA1(Wireshark-win32-3.4.8.exe)=03a4631a76ab74aba471637fd09a818c8a5349fb

Wireshark-win64-3.4.8.msi: 49119232 bytes
SHA256(Wireshark-win64-3.4.8.msi)=d676e4dcf24b324ca1a611669bc6e07653e5b6744ddede8f6eaa371a5f08817d
RIPEMD160(Wireshark-win64-3.4.8.msi)=6b1043a2e9c4494273d64ac240645a0d8dfd2a27
SHA1(Wireshark-win64-3.4.8.msi)=702a10237fe71d0d28a8c64e8d052baba974b184

Wireshark-win32-3.4.8.msi: 43905024 bytes
SHA256(Wireshark-win32-3.4.8.msi)=6d9adaaa7bd1a3b9b1fc1f2d974389f3187ea5b9b4b786d7ac6f11659b962816
RIPEMD160(Wireshark-win32-3.4.8.msi)=082fd79cbf46b7306d22492c6423c327b532c847
SHA1(Wireshark-win32-3.4.8.msi)=7c706280bd98dc38ab14c64be9a118fddfca783c

WiresharkPortable_3.4.8.paf.exe: 38205672 bytes
SHA256(WiresharkPortable_3.4.8.paf.exe)=da8fcaa59b60d6878e5396964d976c4fb8f62cdabb7bdf6aa5dab8c3338d46a4
RIPEMD160(WiresharkPortable_3.4.8.paf.exe)=3f504f1c97a0f62465f482c42fbbaf90a6d4a221
SHA1(WiresharkPortable_3.4.8.paf.exe)=c48f2b48e9c186c81d599b2954f55c21ca0b3b59

Wireshark 3.4.8 Intel 64.dmg: 131051310 bytes
SHA256(Wireshark 3.4.8 Intel 64.dmg)=5e9ac6bc088b1bcca1b34c6848213d66ff8fc1efa4974b9bb1f137198e14f855
RIPEMD160(Wireshark 3.4.8 Intel 64.dmg)=d9d6cb3a9c251e55460773d8df019b7207b67378
SHA1(Wireshark 3.4.8 Intel 64.dmg)=4a019129a27b49f4e0ff496fb3487ceaaf5c1fab

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