Wireshark-announce: [Wireshark-announce] Wireshark 3.0.0rc2 is now available
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Fri, 22 Feb 2019 15:06:01 -0800
I'm proud to announce the release of Wireshark 3.0.0rc2.


 This is the second release candidate for Wireshark 3.0.

 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 user interface improvements have been made. See the “New and
  Updated Features” section below for more details.

  Bug Fixes

   The following bugs have been fixed:

     • Data following a TCP ZeroWindowProbe is marked as retransmission
       and not passed to subdissectors (Bug 15427[1])

     • Lua Error on startup: init.lua: dofile has been disabled due to
       running Wireshark as superuser (Bug 15489[2]).

   Text and Image columns were handled incorrectly for TDS 7.0 and 7.1.
   (Bug 3098[3])

   Dumpcap might not quit if Wireshark or TShark crashes. (Bug 1419[4])

  New and Updated Features

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

     • The IP map feature (the “Map” button in the “Endpoints” dialog)
       has been added back in a modernized form (Bug 14693[5]).

     • The macOS package now ships with Qt 5.12.1. Previously it shipped
       with Qt 5.9.7.

     • The macOS package requires version 10.12 or later. If you’re
       running an older version of macOS, please use Wireshark 2.6.

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

     • Wireshark now supports the Swedish and Ukrainian languages.

     • Initial support for using PKCS #11 tokens for RSA decryption in
       TLS. This can be configured at Preferences, RSA Keys.

     • The build system now produces reproducible builds (Bug 15163[6]).

     • The Windows installers now ship with Qt 5.12.1. Previously they
       shipped with Qt 5.12.0.

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

     • The Windows .exe installers now ship with Npcap instead of
       WinPcap.

     • Conversation timestamps are supported for UDP/UDP-Lite protocols

     • TShark now supports the -G elastic-mapping option which generates
       an ElasticSearch mapping file.

     • The “Capture Information” dialog has been added back (Bug
       12004[7]).

     • The Ethernet and IEEE 802.11 dissectors no longer validate the
       frame check sequence (checksum) by default.

     • The TCP dissector gained a new “Reassemble out-of-order segments”
       preference to fix dissection and decryption issues in case TCP
       segments are received out-of-order. See the User’s Guide, chapter
       TCP Reassembly for details.

     • Decryption support for the new WireGuard dissector (Bug 15011[8],
       requires Libgcrypt 1.8).

     • The BOOTP dissector has been renamed to DHCP. With the exception
       of “bootp.dhcp”, the old “bootp.*” display filter fields are
       still supported but may be removed in a future release.

     • The SSL dissector has been renamed to TLS. As with BOOTP the old
       “ssl.*” display filter fields are supported but may be removed in
       a future release.

     • Coloring rules, IO graphs, Filter Buttons and protocol preference
       tables can now be copied from other profiles using a button in
       the corresponding configuration dialogs.

     • APT-X has been renamed to aptX.

     • When importing from hex dump, it’s now possible to add an
       ExportPDU header with a payload name. This calls the specific
       dissector directly without lower protocols.

     • The sshdump and ciscodump extcap interfaces can now use a proxy
       for the SSH connection.

     • Dumpcap now supports the -a packets:NUM and -b packets:NUM
       options.

     • Wireshark now includes a “No Reassembly” configuration profile.

     • Wireshark now supports the Russian language.

     • The build system now supports AppImage packages.

     • The Windows installers now ship with Qt 5.12.0. Previously they
       shipped with Qt 5.9.7.

     • Support for DTLS and TLS decryption using pcapng files that embed
       a Decryption Secrets Block (DSB) containing a TLS Key Log (Bug
       15252[9]).

     • The editcap utility gained a new --inject-secrets option to
       inject an existing TLS Key Log file into a pcapng file.

     • A new dfilter function string() has been added. It allows the
       conversion of non-string fields to strings so string functions
       (as contains and matches) can be used on them.

     • The Bash test suite has been replaced by one based on Python
       unittest/pytest.

     • The custom window title can now show file path of the capture
       file and it has a conditional separator.

  Removed Features and Support

     • The legacy (GTK+) user interface has been removed and is no
       longer supported.

     • The portaudio library is no longer needed due to the removal of
       GTK+.

     • Wireshark requires Qt 5.2 or later. Qt 4 is no longer supported.

     • Wireshark requires GLib 2.32 or later.

     • Wireshark requires GnuTLS 3.2 or later as optional dependency.

     • Building Wireshark requires Python 3.4 or newer, Python 2.7 is
       unsupported.

     • Building Wireshark requires CMake. Autotools is no longer
       supported.

     • TShark’s -z compare option was removed.

     • Building with Cygwin is no longer supported on Windows.

  New File Format Decoding Support

   Ruby Marshal format

  New Protocol Support

   Apple Wireless Direct Link (AWDL), Basic Transport Protocol (BTP),
   BLIP Couchbase Mobile (BLIP), CDMA 2000, Circuit Emulation Service
   over Ethernet (CESoETH), Cisco Meraki Discovery Protocol (MDP),
   Distributed Ruby (DRb), DXL, E1AP (5G), EVS (3GPP TS 26.445 A.2 EVS
   RTP), Exablaze trailers, General Circuit Services Notification
   Application Protocol (GCSNA), GeoNetworking (GeoNw), GLOW Lawo
   Emberplus Data format, Great Britain Companion Specification (GBCS)
   used in the Smart Metering Equipment Technical Specifications
   (SMETS), GSM-R (User-to-User Information Element usage),
   HI3CCLinkData, Intelligent Transport Systems (ITS) application level,
   ISO 13400-2 Diagnostic communication over Internet Protocol (DoIP),
   ITU-t X.696 Octet Encoding Rules (OER), Local Number Portability
   Database Query Protocol (ANSI), MsgPack, NGAP (5G), NR (5G) PDCP,
   Osmocom Generic Subscriber Update Protocol (GSUP), PCOM protocol,
   PKCS#10 (RFC2986 Certification Request Syntax), PROXY (v2), S101 Lawo
   Emberplus transport frame, Secure Reliable Transport Protocol (SRT),
   Spirent Test Center Signature decoding for Ethernet and FibreChannel
   (STCSIG, disabled by default), Sybase-specific portions of TDS,
   systemd Journal Export, TeamSpeak 3 DNS, TPM 2.0, Ubiquiti Discovery
   Protocol (UBDP), WireGuard, XnAP (5G), and Z39.50 Information
   Retrieval Protocol

  Updated Protocol Support

   Too many protocols have been updated to list here.

  New and Updated Capture File Support

   RFC 7468 (PEM), Ruby marshal object files, systemd Journal Export,
   and Unigraf DPA-400 DisplayPort AUX channel monitor

  New and Updated Capture Interfaces support

   dpauxmon, an external capture interface (extcap) that captures
   DisplayPort AUX channel data from linux kernel drivers.

   sdjournal, an extcap that captures systemd journal entries.

  Major API Changes

     • Lua: the various logging functions (debug, info, message, warn
       and critical) have been removed. Use the print function instead
       for debugging purposes.

     • Lua: on Windows, file-related functions such as dofile now assume
       UTF-8 paths instead of the local code page. This is consistent
       with Linux and macOS and improves compatibility on non-English
       systems. (Bug 15118[10])

 Getting Wireshark

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

  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[12] 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/[13]

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

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

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

 Frequently Asked Questions

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

  Last updated 2019-02-22 21:15:06 UTC

 References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15427
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15489
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3098
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14693
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15163
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12004
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15011
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15252
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15118
  11. https://www.wireshark.org/download.html
  12. https://www.wireshark.org/download.html#thirdparty
  13. https://www.wireshark.org/docs/
  14. https://ask.wireshark.org/
  15. https://www.wireshark.org/lists/
  16. https://bugs.wireshark.org/
  17. http://www.wiresharktraining.com/
  18. https://www.wireshark.org/faq.html


Digests

wireshark-3.0.0rc2.tar.xz: 30942776 bytes
SHA256(wireshark-3.0.0rc2.tar.xz)=27bf2fcd9d4c364dd46a9f9523f8d478da7b603349098699c729081e8fb27ae0
RIPEMD160(wireshark-3.0.0rc2.tar.xz)=d7d60e0be7e456e322521ca16302079b9e21f6a1
SHA1(wireshark-3.0.0rc2.tar.xz)=08a07414fbaecfe18e23aaf15f64839e20b5d75b

Wireshark-win64-3.0.0rc2.exe: 59477136 bytes
SHA256(Wireshark-win64-3.0.0rc2.exe)=036f59819d857563d30fefd32c5e1ed49cb99ebc1b1ce16fea1f1f55ed4d36a4
RIPEMD160(Wireshark-win64-3.0.0rc2.exe)=2b062daea432cb9a9d90e41e73ab04a3c405d3ba
SHA1(Wireshark-win64-3.0.0rc2.exe)=cf301f3acc9a8535e95d4c85ad2d31d02483c091

Wireshark-win32-3.0.0rc2.exe: 54211640 bytes
SHA256(Wireshark-win32-3.0.0rc2.exe)=674e50f6d54b0330a69ccd2ea2c8656ee49a33139d79945aef09acfc6fb3e50e
RIPEMD160(Wireshark-win32-3.0.0rc2.exe)=86111f95c671936908dac733eee445fe51de6a79
SHA1(Wireshark-win32-3.0.0rc2.exe)=a721c7037a62bb7a21f83ebdee1d07eeff10b85a

Wireshark-win64-3.0.0rc2.msi: 47312896 bytes
SHA256(Wireshark-win64-3.0.0rc2.msi)=4ba08524be620572227ec81de966155c7dc687b84cd31345ad37a3629d87707d
RIPEMD160(Wireshark-win64-3.0.0rc2.msi)=60ed73fda04ba4607614c836195590585fb9f695
SHA1(Wireshark-win64-3.0.0rc2.msi)=3db847ad0de83105eea48355c39975a97dc5db02

Wireshark-win32-3.0.0rc2.msi: 42106880 bytes
SHA256(Wireshark-win32-3.0.0rc2.msi)=21b55269b87f298510cf97daf507ea14de4fcca3760a8ae95782bc2ccd3aa36b
RIPEMD160(Wireshark-win32-3.0.0rc2.msi)=ce5720c89e509e6717e77ed9e206bb22700fc3da
SHA1(Wireshark-win32-3.0.0rc2.msi)=83fdd767fd065d227a3a25464ab3dbf444d8317a

WiresharkPortable_3.0.0rc2.paf.exe: 35917480 bytes
SHA256(WiresharkPortable_3.0.0rc2.paf.exe)=6a3072f687c39ccb456792028c0872ece92a742f31d6b30c44b97d947fe5503d
RIPEMD160(WiresharkPortable_3.0.0rc2.paf.exe)=155f32f9ee8efac83278b6093609dca5e5103ead
SHA1(WiresharkPortable_3.0.0rc2.paf.exe)=753d0e8ea6908a3851ea5e65d753e7efa4817fc0

Wireshark 3.0.0rc2 Intel 64.dmg: 86694823 bytes
SHA256(Wireshark 3.0.0rc2 Intel
64.dmg)=7bcfc7244d787fe1e19e19ee10aa42b924b48a1a5307d866d7837e0378b87a07
RIPEMD160(Wireshark 3.0.0rc2 Intel
64.dmg)=5ac5351a37647a977d48c4e8b34e2d519fb73e42
SHA1(Wireshark 3.0.0rc2 Intel 64.dmg)=121c14d5747c2e8c7be47f1e629d4be7cc050ac8

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