Wireshark · Wireshark-announce: [Wireshark-announce] Wireshark 3.3.0 is now available

[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 This is an experimental release intended to test new features 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.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.

     • “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.

  New Protocol Support

   Arinc 615A (A615A), Asphodel Protocol, AudioCodes Debug Recording
   (ACDR), Bluetooth HCI ISO (BT HCI ISO), Cisco MisCabling Protocol
   (MCP), DCE/RPC IRemoteWinspool SubSystem, (IREMOTEWINSPOOL), Dynamic
   Link Exchange Protocol (DLEP), Fortinet Single Sign-on (FSSO), FTDI
   Multi-Protocol Synchronous Serial Engine (FTDI MPSSE), Hypertext
   Transfer Protocol Version 3 (HTTP3), 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[3] 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[4] 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[5].

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

 Frequently Asked Questions

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

  Last updated 2020-09-15 21:50:40 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://www.wireshark.org/download.html#thirdparty
   4. https://ask.wireshark.org/
   5. https://www.wireshark.org/lists/
   6. https://gitlab.com/wireshark/wireshark/-/issues
   7. https://www.wireshark.org/faq.html


Digests

wireshark-3.3.0.tar.xz: 32795500 bytes
SHA256(wireshark-3.3.0.tar.xz)=925cecf41f5d9c1ed6a9236de4ee283eaef40fe503208fe7e767486436a1f613
RIPEMD160(wireshark-3.3.0.tar.xz)=ee123833ef2577ead58c36e97384d136fbae3694
SHA1(wireshark-3.3.0.tar.xz)=b2dfe005d3a4119dddc49b29f9ec1be13b163a56

Wireshark-win32-3.3.0.exe: 56311976 bytes
SHA256(Wireshark-win32-3.3.0.exe)=2ae350fb782ce5cd1f5f7a2feb2357630457a06483574b3ec50261d5551d2543
RIPEMD160(Wireshark-win32-3.3.0.exe)=8b447f94493a7774aa2e62c116ec0983c26da6c1
SHA1(Wireshark-win32-3.3.0.exe)=815c05cbf8fb060cf1b49051061a17cf2bcac0ad

Wireshark-win64-3.3.0.exe: 61407968 bytes
SHA256(Wireshark-win64-3.3.0.exe)=d13f62816f7eb0ac533482a599993d25e9b768518d5ecb7a73002176c4b0db13
RIPEMD160(Wireshark-win64-3.3.0.exe)=2f966a67b1d420bfe7c649edac856ca0fab99508
SHA1(Wireshark-win64-3.3.0.exe)=2897572347d2bfdd8f49ed149e4873fb61c804c0

Wireshark-win64-3.3.0.msi: 49205248 bytes
SHA256(Wireshark-win64-3.3.0.msi)=26c8b338e979df5e9daa45749c73bb45bfe1e36b3ef9cd17292a3b27a93487d2
RIPEMD160(Wireshark-win64-3.3.0.msi)=66d5c623a81fe11eccba8f337263101a1fd623e2
SHA1(Wireshark-win64-3.3.0.msi)=5155fa4927ee597ef12540f20bc39919718598e8

Wireshark-win32-3.3.0.msi: 43991040 bytes
SHA256(Wireshark-win32-3.3.0.msi)=0911d5c4a1b5f7a5b4a46a104b744acde194f45399d5b2ec2ed1bc6651e936a9
RIPEMD160(Wireshark-win32-3.3.0.msi)=aee3ef355b28ed66448a28a16f1662ab7b4ea8d5
SHA1(Wireshark-win32-3.3.0.msi)=260af26b692b4e6d65fe443b412d6f099f984e96

WiresharkPortable_3.3.0.paf.exe: 114162840 bytes
SHA256(WiresharkPortable_3.3.0.paf.exe)=fd472fc38495998c2789732a6d157e64342bab7d1e0b7db81ac3baff58cdb84a
RIPEMD160(WiresharkPortable_3.3.0.paf.exe)=04a3e0b4ad488badff8b89dfe142a4dcdb3d5317
SHA1(WiresharkPortable_3.3.0.paf.exe)=8366b5a4357217f1521f1d0163dcaf4d9519731a

Wireshark 3.3.0 Intel 64.dmg: 127405522 bytes
SHA256(Wireshark 3.3.0 Intel 64.dmg)=fee4c36a9a359b9ec34e6b8f17521b8f052528277d16b173c6aa73d7c248da7d
RIPEMD160(Wireshark 3.3.0 Intel 64.dmg)=3789b7815d9484f2601b9529e71513c345e314ef
SHA1(Wireshark 3.3.0 Intel 64.dmg)=295711cc60150e66832d84c4be2585ee94f9cdbb

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