Wireshark-announce: [Wireshark-announce] Wireshark 3.1.0 is now available
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <[email protected]>
Date: Thu, 25 Jul 2019 12:52:37 -0700
I'm proud to announce the release of Wireshark 3.1.0.


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

     • Drag&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"

     • Drag&Drop a column entry to the display filter to create a filter
       for it

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

  New Protocol Support

   3GPP BICC MST (BICC-MST), 3GPP log packet (LOG3GPP), 3GPP/GSM Cell
   Broadcast Service Protocol (cbsp), 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, 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), MIDI System Exclusive DigiTech
   (SYSEX DigiTech), Network Controller Sideband Interface (NCSI), NR
   Positioning Protocol A (NRPPa) TS 38.455, and NVM Express over
   Fabrics for TCP (nvme-tcp)

  Updated Protocol Support

   Too many protocols have been updated to list here.

  New and Updated Capture File Support

   3gpp phone, Android Logcat Text, Ascend, 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-07-25 19:11:31 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.1.0.tar.xz: 31052040 bytes
SHA256(wireshark-3.1.0.tar.xz)=a7b54f9e35fc69291dcac5104ecbef8260534a75dec5b8105605b6c423fd3de3
RIPEMD160(wireshark-3.1.0.tar.xz)=97aa4bead16bc4de841411375720ff141500f72f
SHA1(wireshark-3.1.0.tar.xz)=ecb40dca04b3a9b4e6317927754335b493ddb845

Wireshark-win64-3.1.0.exe: 68767512 bytes
SHA256(Wireshark-win64-3.1.0.exe)=4083688720306deccd4ff211ac4405019d820bc2c818f0f388bb85cd88053480
RIPEMD160(Wireshark-win64-3.1.0.exe)=d7d80b01baa6d0480513c273d38590b6e3a52ad3
SHA1(Wireshark-win64-3.1.0.exe)=1ce88c20c7a30e2cbea33a3c7c7faf6182a9aa1a

Wireshark-win32-3.1.0.exe: 63539048 bytes
SHA256(Wireshark-win32-3.1.0.exe)=b53ff95f10f295d8d93027a514d8682a9e42c639ccc4e70a29b90930f6dd3d3c
RIPEMD160(Wireshark-win32-3.1.0.exe)=194742af3d19d239e7063c64d753684c937543c0
SHA1(Wireshark-win32-3.1.0.exe)=58bfc066583343ed9542953162f9c24547fb4ff1

Wireshark-win64-3.1.0.msi: 47886336 bytes
SHA256(Wireshark-win64-3.1.0.msi)=821f663af151035fdfe2375f98227cd060c24dd8d670af4adbfff36abd2ae70a
RIPEMD160(Wireshark-win64-3.1.0.msi)=9e95a35f1d239551ca9a9a035b852669c1805b29
SHA1(Wireshark-win64-3.1.0.msi)=d94f3e41891c01a0a8007a90e9962d62cf9a6621

Wireshark-win32-3.1.0.msi: 42557440 bytes
SHA256(Wireshark-win32-3.1.0.msi)=865028d94fc68443dcd9e99c7f2e692b392693c43aac8d3368b103249d373926
RIPEMD160(Wireshark-win32-3.1.0.msi)=3e0d799fdd2febab07ac62691aca07154751a3f9
SHA1(Wireshark-win32-3.1.0.msi)=590d239eb053da45316a03c9bd6af782bc3882e3

WiresharkPortable_3.1.0.paf.exe: 36183480 bytes
SHA256(WiresharkPortable_3.1.0.paf.exe)=03b02abcd12de97f4bef0c1ae4752ab8e476b45e7becfbdcc7a36a0113974c2e
RIPEMD160(WiresharkPortable_3.1.0.paf.exe)=37f4795d70a56a35ead09568ff1c10e8a692e791
SHA1(WiresharkPortable_3.1.0.paf.exe)=e281eb4a2602e72304e016704b9af46aad3289c2

Wireshark 3.1.0 Intel 64.dmg: 94412297 bytes
SHA256(Wireshark 3.1.0 Intel
64.dmg)=c85d41219a283677c28a3b7eac96da76d0332d434510c082ae35633bde7e2ed9
RIPEMD160(Wireshark 3.1.0 Intel
64.dmg)=a441236c1fe289021a0c64bdd3edf3341a69941f
SHA1(Wireshark 3.1.0 Intel 64.dmg)=9b8943ee6fa0b310a68c2998eae49ace7687774d

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