[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.4.0rc1.


 This is the first release candidate for Wireshark 3.4.

 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

  Many improvements have been made. See the “New and Updated Features”
  section below for more details.

  New and Updated Features

   The following features are new (or have been significantly updated)
   since version 3.3.1:

     • The Protobuf fields defined as google.protobuf.Timestamp type of
       Protobuf standard library can now be dissected as Wireshark
       fields of absolute time type.

   The following features are new (or have been significantly updated)
   since version 3.3.0:

     • The Windows installers now ship with Npcap 1.00. They previously
       shipped with Npcap 0.9997.

     • The Windows installers now ship with Qt 5.15.1. They previously
       shipped with Qt 5.12.8.

   The following features are new (or have been significantly updated)
   since version 3.2.0:

     • Windows executables and installers are now signed using SHA-2
       only[1].

     • Save RTP stream to .au supports any codec with 8000 Hz rate
       supported by Wireshark (shown in RTP player). If save of audio is
       not possible (unsupported codec or rate), silence of same length
       is saved and warning is shown.

     • Asynchronous DNS resolution is always enabled. As a result, the
       c-ares library is now a required dependency.

     • Protobuf fields can be dissected as Wireshark (header) fields
       that allows user input the full names of Protobuf fields or
       messages in Filter toolbar for searching.

     • Dissectors based on Protobuf can register themselves to a new
       'protobuf_field' dissector table, which is keyed with the full
       names of fields, for further parsing fields of BYTES or STRING
       type.

     • Wireshark is able to decode, play, and save iLBC payload on
       platforms where the iLBC library[2] is available.

     • Wireshark is able to decode, play, and save opus payload on
       platforms where the opus library[3] is available.

     • “Decode As” entries can now be copied from other profiles using a
       button in the dialog.

     • sshdump can now be copied to multiple instances. Each instance
       will show up a different interface and will have its own profile.

     • The main window now supports a packet diagram view, which shows
       each packet as a textbook-style diagram.

     • Filter buttons (“Preferences → Filter Buttons”) can be grouped by
       using “//” as a path separator in the filter button label.

     • IPP Over USB packets can now be dissected and displayed

  New Protocol Support

   Arinc 615A (A615A), Asphodel Protocol, AudioCodes Debug Recording
   (ACDR), Bluetooth HCI ISO (BT HCI ISO), Cisco MisCabling Protocol
   (MCP), Community ID Flow Hashing (CommunityID), DCE/RPC
   IRemoteWinspool SubSystem, (IREMOTEWINSPOOL), Dynamic Link Exchange
   Protocol (DLEP), EAP Generalized Pre-Shared Key (EAP-GPSK), EAP
   Password Authenticated Exchange (EAP-PAX), EAP Pre-Shared Key
   (EAP-PSK), EAP Shared-secret Authentication and Key Establishment
   (EAP-SAKE), Fortinet Single Sign-on (FSSO), FTDI Multi-Protocol
   Synchronous Serial Engine (FTDI MPSSE), Hypertext Transfer Protocol
   Version 3 (HTTP3), ILDA Digital Network (IDN), Java Debug Wire
   Protocol (JDWP), LBM Stateful Resolution Service (LBMSRS), Lithionics
   Battery Management, OBSAI UDP-based Communication Protocol (UDPCP),
   Palo Alto Heartbeat Backup (PA-HB-Bak), ScyllaDB RPC, Technically
   Enhanced Capture Module Protocol (TECMP), Tunnel Extensible
   Authentication Protocol (TEAP), UDP based FTP w/ multicast V5
   (UFTP5), and USB Printer (USBPRINTER)

  Updated Protocol Support

   Too many protocols have been updated to list here.

  New and Updated Capture File Support

   MP4 (ISO/IEC 14496-12)

 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 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’sQ&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].

 Frequently Asked Questions

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

  Last updated 2020-10-22 22:40:20 UTC

 References

   1. https://support.microsoft.com/en-us/help/4472027/2019-sha-2-code-s
  igning-support-requirement-for-windows-and-wsus
   2. https://github.com/TimothyGu/libilbc
   3. https://opus-codec.org/
   4. https://www.wireshark.org/download.html#thirdparty
   5. https://ask.wireshark.org/
   6. https://www.wireshark.org/lists/
   7. https://gitlab.com/wireshark/wireshark/-/issues
   8. https://www.wireshark.org/faq.html


Digests

wireshark-3.4.0rc1.tar.xz: 32500352 bytes
SHA256(wireshark-3.4.0rc1.tar.xz)=b6a3409585ea2e23bdf71741ada298b896b637d63aee7a022ea1d30d0098ecdd
RIPEMD160(wireshark-3.4.0rc1.tar.xz)=b40268598426ce777a7597d249be857f14163d4b
SHA1(wireshark-3.4.0rc1.tar.xz)=a448d96bcce2ee274a8d0a2ff7dcf747b0a9fcb0

Wireshark-win64-3.4.0rc1.exe: 61367144 bytes
SHA256(Wireshark-win64-3.4.0rc1.exe)=b2fa0c68cab78f8c52388cf4b08deea6bcaf14272716235d35a29704b2d731e2
RIPEMD160(Wireshark-win64-3.4.0rc1.exe)=701f8fbca69bba26a56fe10e0a9a78b02c131b3d
SHA1(Wireshark-win64-3.4.0rc1.exe)=05a87e87453ecc34cdbffc4b688e47c0a29aef5c

Wireshark-win32-3.4.0rc1.exe: 56423320 bytes
SHA256(Wireshark-win32-3.4.0rc1.exe)=9b14062f8f160c533e30c2f319f95afc479bdca5e2f4f28e8a8c9bfb24ce389f
RIPEMD160(Wireshark-win32-3.4.0rc1.exe)=41ec3838830d82ff64d1c4c685e2d00a4af0e20f
SHA1(Wireshark-win32-3.4.0rc1.exe)=8a041877b18f7b7373597bc11e7d3834044b8cc1

Wireshark-win32-3.4.0rc1.msi: 44675072 bytes
SHA256(Wireshark-win32-3.4.0rc1.msi)=e76a9489b466efff4bfa2820dfe960d7cda0a5f53760595d2046a71617383836
RIPEMD160(Wireshark-win32-3.4.0rc1.msi)=0b0464e0d3c429e3e99855ee1742e8a99faca2b8
SHA1(Wireshark-win32-3.4.0rc1.msi)=fc9e7b774647a3acafbef52325ce4933d393f3a5

Wireshark-win64-3.4.0rc1.msi: 49745920 bytes
SHA256(Wireshark-win64-3.4.0rc1.msi)=2078b6a7243a04c477aef68be8884ce344bf09f8aa4ecdafc3dcb34f788dbfac
RIPEMD160(Wireshark-win64-3.4.0rc1.msi)=23c192b641c423f0c43cadc14263f5ef124bf98b
SHA1(Wireshark-win64-3.4.0rc1.msi)=6a34186d82e51eaf95b05e08e235abb7178276af

WiresharkPortable_3.4.0rc1.paf.exe: 115366568 bytes
SHA256(WiresharkPortable_3.4.0rc1.paf.exe)=71358f455165b7d3f9d1b01f9ea89c213c8c66a06688b337d660da019f06b139
RIPEMD160(WiresharkPortable_3.4.0rc1.paf.exe)=5a24617cc9923733ac4e4b6750a4ad825e70dd92
SHA1(WiresharkPortable_3.4.0rc1.paf.exe)=63a2409251df46f2c7d8ee8ebf4b6eec9f1d7677

Wireshark 3.4.0rc1 Intel 64.dmg: 127586348 bytes
SHA256(Wireshark 3.4.0rc1 Intel 64.dmg)=9c1b83f4e509155c8a899edca4f0dbd546e21bd60fa872cfa3f8a39a2a914f0e
RIPEMD160(Wireshark 3.4.0rc1 Intel 64.dmg)=e1e142cf4f25f15c6c9405aa2106bbe03d8e6578
SHA1(Wireshark 3.4.0rc1 Intel 64.dmg)=ff6fc3576cef824300d09189f8f22c4b163720a0

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