Wireshark · Wireshark-announce: [Wireshark-announce] Wireshark 3.2.0rc1 is now available

Wireshark-announce: [Wireshark-announce] Wireshark 3.2.0rc1 is now available

From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>

Date: Thu, 5 Dec 2019 12:15:57 -0800

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

This is the first release candidate for Wireshark 3.2.

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.1.1:

• Miscellaneous UI fixes and updates.

• The macOS installer now ships with Qt 5.12.6. It previously
shipped with Qt 5.12.5.

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

• Automatic updates are supported on macOS.

• You can now select multiple packets in the packet list at the
same time

• They can be exported as Text by “Ctrl+C” or “Cmd+C” and the
corresponding menu in “Edit › Copy › As …”

• They can be marked/unmarked or ignored/unignored at the same time

• They can be exported and printed using the corresponding menu
entries “File › Export Specified Packets”, “File › Export Packet
Dissections” and “File › Print”

You can now follow HTTP/2 and QUIC streams.

You can once again mark and unmark packets using the middle mouse
button. This feature went missing around 2009 or so.

The Windows packages are now built using Microsoft Visual Studio
2019.

IOGraph automatically adds a graph for the selected display filter if
no previous graph exists

Action buttons for the display filter bar may be aligned left via the
context menu

• The "Expression…" toolbar entry has been moved to "Analyze ›
Display filter Expression …" as well as to the context menu of
the display filter toolbar

Allow extcaps to be loaded from the personal configuration directory

The Wireshark 3.1.0 Windows installers ship with Qt 5.12.6. Previous
installers shipped with Qt 5.12.4.

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

• You can drag and drop a field to a column header to create a
column for that field, or to the display filter input to create a
display filter. If a display filter is applied, the new filter
can be added using the same rules as “Apply Filter”

• You can drag and drop a column entry to the display filter to
create a filter for it.

• You can import profiles from a .zip archive or an existing
directory.

• Dark mode support on macOS and dark theme support on other
platforms has been improved.

• Brotli decompression support in HTTP/HTTP2 (requires the brotli
library).

• The build system now checks for a SpeexDSP system library
installation. The bundled Speex resampler code is still provided
as a fallback.

• WireGuard decryption can now be enabled through keys embedded in
a pcapng in addition to the existing key log preference (Bug
15571[1]).

• A new tap for extracting credentials from the capture file has
been added. It can be accessed through the -z credentials option
in tshark or from the “Tools › Credentials” menu in Wireshark.

• Editcap can now split files on floating point intervals.

• Windows .msi packages are now signed using SHA-2[2]. .exe
installers are still dual-signed using SHA-1 and SHA-2.

• The “Enabled Protocols” Dialog now only enables, disables and
inverts protocols based on the set filter selection. The protocol
type (standard or heuristic) may also be choosen as a filter
value.

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

• The “Analyze › Apply as Filter” and “Analyze › Prepare a Filter”
packet list and detail popup menus now show a preview of their
respective filters.

• Protobuf files (*.proto) can now be configured to enable more
precise parsing of serialized Protobuf data (such as gRPC).

• HTTP2 support streaming mode reassembly. To use this feature,
subdissectors can register itself to "streaming_content_type"
dissector table and return pinfo→desegment_len and
pinfo→desegment_offset to tell HTTP2 when to start and how many
additional bytes requires when next called.

• The message of stream gRPC method can now be parsed with
supporting of HTTP2 streaming mode reassembly feature.

• The Wireshark 3.1.0 Windows installers ship with Qt 5.12.4.
Previous installers shipped with Qt 5.12.1.

New Protocol Support

3GPP BICC MST (BICC-MST), 3GPP log packet (LOG3GPP), 3GPP/GSM Cell
Broadcast Service Protocol (cbsp), Asynchronous Management Protocol
(AMP), Bluetooth Mesh Beacon, Bluetooth Mesh PB-ADV, Bluetooth Mesh
Provisioning PDU, Bluetooth Mesh Proxy, CableLabs Layer-3 Protocol
IEEE EtherType 0xb4e3 (CL3), DCOM IProvideClassInfo, DCOM ITypeInfo,
Diagnostic Log and Trace (DLT), Distributed Replicated Block Device
(DRBD), Dual Channel Wi-Fi (CL3DCW), EBHSCR Protocol (EBHSCR), EERO
Protocol (EERO), evolved Common Public Radio Interface (eCPRI), File
Server Remote VSS Protocol (FSRVP), FTDI FT USB Bridging Devices
(FTDI FT), Graylog Extended Log Format over UDP (GELF), GSM/3GPP CBSP
(Cell Broadcast Service Protocol), ITS message - CAMv1, ITS message -
DENMv1, Linux net_dm (network drop monitor) protocol, MIDI System
Exclusive DigiTech (SYSEX DigiTech), Network Controller Sideband
Interface (NCSI), NR Positioning Protocol A (NRPPa) TS 38.455, NVM
Express over Fabrics for TCP (nvme-tcp), OsmoTRX Protocol (GSM
Transceiver control and data), Scalable service-Oriented MiddlewarE
over IP (SOME/IP), USB 2.0 Link Layer (USBLL), and Wi-Fi Neighbour
Awareness Networking (NAN)

Updated Protocol Support

Too many protocols have been updated to list here.

New and Updated Capture File Support

3gpp phone, Android Logcat Text, Ascend, Busmaster log file, Candump,
Endace ERF, NetScaler, pcapng, and Savvius *Peek

Getting Wireshark

Wireshark source code and installation packages are available from
https://www.wireshark.org/download.html[3].

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/[5]

Community support is available on Wireshark’s Q&A site[6] 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[7].

Bugs and feature requests can be reported on the bug tracker[8].

Official Wireshark training and certification are available from
Wireshark University[9].

Frequently Asked Questions

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

Last updated 2019-12-05 19:58:02 UTC

References

1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15571
2. https://support.microsoft.com/en-us/help/4472027/2019-sha-2-code-s
igning-support-requirement-for-windows-and-wsus
3. https://www.wireshark.org/download.html
4. https://www.wireshark.org/download.html#thirdparty
5. https://www.wireshark.org/docs/
6. https://ask.wireshark.org/
7. https://www.wireshark.org/lists/
8. https://bugs.wireshark.org/
9. https://www.wiresharktraining.com/
10. https://www.wireshark.org/faq.html

Digests

wireshark-3.2.0rc1.tar.xz: 31426064 bytes
SHA256(wireshark-3.2.0rc1.tar.xz)=1c998aaf29306969ad6eba2fbbfc26603a38d84a50afec77dd14367e3889c3fa
RIPEMD160(wireshark-3.2.0rc1.tar.xz)=03e41971dd8ed1c1a8f53efa1e440c72b13dd49f
SHA1(wireshark-3.2.0rc1.tar.xz)=36c8088fc602900044f2b3d446b8faf3e1b74bea

Wireshark-win32-3.2.0rc1.exe: 63829624 bytes
SHA256(Wireshark-win32-3.2.0rc1.exe)=b255abe473c75b6f72fdd6316cf579a239ba3845d91aa6e009dcf6ba5358c18e
RIPEMD160(Wireshark-win32-3.2.0rc1.exe)=c7ff08a0c3c4aec2eda5cd2602164bd2c2fd9698
SHA1(Wireshark-win32-3.2.0rc1.exe)=b1ff48b4569fbfb6dd102b955805268e8c5569d3

Wireshark-win64-3.2.0rc1.exe: 69054816 bytes
SHA256(Wireshark-win64-3.2.0rc1.exe)=592ccec8245bf17221eeb44f0b23f97f0dedbd2eb25032f94ccd78d64def832f
RIPEMD160(Wireshark-win64-3.2.0rc1.exe)=84989628ce61cbe6ac31523965ae1702f498da37
SHA1(Wireshark-win64-3.2.0rc1.exe)=c44242138e904ee7f6c1b212490aae21bd2d018d

Wireshark-win32-3.2.0rc1.msi: 42913792 bytes
SHA256(Wireshark-win32-3.2.0rc1.msi)=994fdd5803a79280b8df108a5a638292c8ff341b444453729449e09f4b98576d
RIPEMD160(Wireshark-win32-3.2.0rc1.msi)=aa3dad7d937c6026c1cf66585c80322fd14333c4
SHA1(Wireshark-win32-3.2.0rc1.msi)=4be2dcca46a7968764540c81763d248d9517f324

Wireshark-win64-3.2.0rc1.msi: 48205824 bytes
SHA256(Wireshark-win64-3.2.0rc1.msi)=94177af349ed8a9a075cbe3b58b24a353d5b22f1aa73db3b8ef26e84fc73ad72
RIPEMD160(Wireshark-win64-3.2.0rc1.msi)=99770531dcca1dc7912b5f68223f3fe91274420f
SHA1(Wireshark-win64-3.2.0rc1.msi)=c53fcf23f23d6e4865e2f12fc40d118ba2d2a090

WiresharkPortable_3.2.0rc1.paf.exe: 36517600 bytes
SHA256(WiresharkPortable_3.2.0rc1.paf.exe)=624eb9d34ab1cef54c81fef569d4a6f9d9ef41d8f35102bd45a0dc5965f34a23
RIPEMD160(WiresharkPortable_3.2.0rc1.paf.exe)=837cbc57151bed9543a0743eaf7824f6a5e7c5b3
SHA1(WiresharkPortable_3.2.0rc1.paf.exe)=dacc6d56a94f2cc11bc69de53fae21e2be0d4f90

Wireshark 3.2.0rc1 Intel 64.dmg: 96413777 bytes
SHA256(Wireshark 3.2.0rc1 Intel
64.dmg)=72bea8b03fa5e49b990480f1d564454ca58dab382460c5d6a94c05e2efdc5b50
RIPEMD160(Wireshark 3.2.0rc1 Intel
64.dmg)=c70075dfac5734aeb6f2c86129c25e06fbd348ea
SHA1(Wireshark 3.2.0rc1 Intel 64.dmg)=6ef30609dd050c7563ee155897e0a87fcf52ed26

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

Prev by Date: [Wireshark-announce] Wireshark 2.6.13 is now available
Next by Date: [Wireshark-announce] Wireshark 3.2.0rc2 is now available
Previous by thread: [Wireshark-announce] Wireshark 2.6.13 is now available
Next by thread: [Wireshark-announce] Wireshark 3.2.0rc2 is now available
Index(es):
- Date
- Thread