Wireshark-announce: [Wireshark-announce] Wireshark 3.4.9 is now available

Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Wed, 6 Oct 2021 12:29:12 -0700
I'm proud to announce the release of Wireshark 3.4.9.


 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:

     • TShark PDML output embeds "proto" elements within other "proto"
       elements Issue 10588[1].

     • Filter expressions comparing against single-octet hex strings
       where the hex digit string equals a protocol name don’t work
       Issue 12810[2].

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

     • IEEE 802.15.4: Missing check on "PAN ID Present" bit of the
       Multipurpose Frame Control field Issue 17496[4].

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

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

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

     • Error when reloading lua plugins with a capture file loaded via a
       custom lua file handler Issue 17615[8].

     • Absolute time UTC field filters are constructed incorrectly,
       don’t match the packet Issue 17617[9].

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

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

     • BT-DHT reports malformed packets that are actually uTP on same
       connection Issue 17626[12].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   AMQP, Aruba IAP, BGP, BT-DHT, CoAP, DCERPC SPOOLSS, Diameter, EPL,
   GSM A-bis OML, GSM A-I/F COMMON, GSM SIM, IEEE 1905.1a, IEEE
   802.15.4, IMAP, InfiniBand, ISIS LSP, ISObus VT, JPEG, MP2T,
   NORDIC_BLE, QUIC, RTCP, SDP, SMB, TWAMP-Control, USB HID, 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[13] 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[14] 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[15].

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

 Frequently Asked Questions

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

  Last updated 2021-10-06 17:20:36 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/10588
   2. https://gitlab.com/wireshark/wireshark/-/issues/12810
   3. https://gitlab.com/wireshark/wireshark/-/issues/14217
   4. https://gitlab.com/wireshark/wireshark/-/issues/17496
   5. https://gitlab.com/wireshark/wireshark/-/issues/17530
   6. https://gitlab.com/wireshark/wireshark/-/issues/17576
   7. https://gitlab.com/wireshark/wireshark/-/issues/17610
   8. https://gitlab.com/wireshark/wireshark/-/issues/17615
   9. https://gitlab.com/wireshark/wireshark/-/issues/17617
  10. https://gitlab.com/wireshark/wireshark/-/issues/17620
  11. https://gitlab.com/wireshark/wireshark/-/issues/17622
  12. https://gitlab.com/wireshark/wireshark/-/issues/17626
  13. https://www.wireshark.org/download.html#thirdparty
  14. https://ask.wireshark.org/
  15. https://www.wireshark.org/lists/
  16. https://gitlab.com/wireshark/wireshark/-/issues
  17. https://www.wireshark.org/faq.html


Digests

wireshark-3.4.9.tar.xz: 32335284 bytes
SHA256(wireshark-3.4.9.tar.xz)=c6525e829bd24525ee699aa207ecd27c50646d64263a669671badfb71cd99620
RIPEMD160(wireshark-3.4.9.tar.xz)=7fd30ef3b906fa2301b6a77bd4623633d0b46f23
SHA1(wireshark-3.4.9.tar.xz)=0ed390387d9d6201cdd6364e782cb58c8ad4d9ce

Wireshark-win32-3.4.9.exe: 55411320 bytes
SHA256(Wireshark-win32-3.4.9.exe)=c48ccab1dd950582071d885d89881b201aac505163f190c253ab3b9ea2666118
RIPEMD160(Wireshark-win32-3.4.9.exe)=e625c52faa448a6bf0fbfac97371001a4bc2cf3b
SHA1(Wireshark-win32-3.4.9.exe)=1fe4a6091f89151079799185de3a25e575079796

Wireshark-win64-3.4.9.exe: 71374760 bytes
SHA256(Wireshark-win64-3.4.9.exe)=dca0db950d1a9dca9f5653ab0f1110a454d812c9d4224f9acdb1e7e74d8e4513
RIPEMD160(Wireshark-win64-3.4.9.exe)=2c3e87dc951f1523ce5fe815b71a5a123c229b34
SHA1(Wireshark-win64-3.4.9.exe)=fea985c482130a2f92b04e2e3f8bbeb8815c3f5f

Wireshark-win64-3.4.9.msi: 49139712 bytes
SHA256(Wireshark-win64-3.4.9.msi)=5a687a9f2a59325165942b0d587788ea38b1fe9d6e4ba1304fd2390e5ca2b65c
RIPEMD160(Wireshark-win64-3.4.9.msi)=eea1a1f62f76f605837a80692e4c6ebd1157f532
SHA1(Wireshark-win64-3.4.9.msi)=f810820668306ed321a9150e7d2d9316cad8067f

Wireshark-win32-3.4.9.msi: 43913216 bytes
SHA256(Wireshark-win32-3.4.9.msi)=e51d15a55ee71af58a97930ff36ed7f3a441505f222bea1a480adca385bb8b49
RIPEMD160(Wireshark-win32-3.4.9.msi)=118dffe084fcc52cebcf11f847e5c5b37ee8e54e
SHA1(Wireshark-win32-3.4.9.msi)=80b0822e1a205f8f650b9d2670cbeba5a18e5095

WiresharkPortable_3.4.9.paf.exe: 38213520 bytes
SHA256(WiresharkPortable_3.4.9.paf.exe)=357184a0d16f42dcc7980efb0e712bf8f13cfe5882f41badeb01b1226abb7e55
RIPEMD160(WiresharkPortable_3.4.9.paf.exe)=e950f9d00c3ff473c71d0d7043ce9fdbe00dc3a2
SHA1(WiresharkPortable_3.4.9.paf.exe)=239130f251b87b577c4f77b8e91dc359005eb14f

Wireshark 3.4.9 Intel 64.dmg: 131083793 bytes
SHA256(Wireshark 3.4.9 Intel 64.dmg)=2092237599f23064a7004b9123f4026c81b9b3b04d914efdb3c1e79eaee33a3e
RIPEMD160(Wireshark 3.4.9 Intel 64.dmg)=98be4d00db2680800a6fb8cd1eea9c6ec7c17688
SHA1(Wireshark 3.4.9 Intel 64.dmg)=f647eaca9a5537aab86085ce2252a716d1187585

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