[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


   This is a semi-experimental release intended to test new features for
   Wireshark 2.6.
     __________________________________________________________________

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.

  New and Updated Features

   The following features are new (or have been significantly updated)
   since version 2.4.0:
     * Display filter buttons can now be edited, disabled, and removed via
       a context menu directly from the toolbar
     * Drag & Drop filter fields to the display filter toolbar or edit to
       create a button on the fly or apply the filter as a display filter.
     * Application startup time has been reduced.
     * Some keyboard shortcut mix-ups have been resolved by assigning new
       shortcuts to Edit -> Copy methods.
     * TShark now supports color using the --color option.
     * The "matches" display filter operator is now case-insensitive.
     * Display expression (button) preferences have been converted to a
       UAT. This puts the display expressions in their own file. Wireshark
       still supports preference files that contain the old preferences,
       but new preference files will be written without the old fields.
     * SMI private enterprise numbers are now read from the
       "enterprises.tsv" configuration file.
     * The QUIC dissector has been renamed to Google QUIC (quic -> gquic).
     * The selected packet number can now be shown in the Status Bar by
       enabling Preferences -> Appearance -> Layout -> Show selected
       packet number.
     * File load time in the Status Bar is now disabled by default and can
       be enabled in Preferences -> Appearance -> Layout -> Show file load
       time.
     * Support for the G.729A codec in the RTP Player is now added via the
       bcg729 library.
     * Support for hardware-timestamping of packets has been added.
     * Improved NetMon .cap support with comments, event tracing, network
       filter, network info types and some Message Analyzer exported
       types.
     * The personal plugins folder on Linux/Unix is now
       ~/.local/lib/wireshark/plugins.
     * TShark can print flow graphs using -z flow...
     * Capinfos now prints SHA256 hashes in addition to RIPEMD160 and
       SHA1. MD5 output has been removed.
     * The packet editor has been removed. (This was a GTK+ only
       experimental feature.)
     * Support BBC micro:bit Bluetooth profile
     * The Linux and UNIX installation step for Wireshark will now install
       headers required to build plugins. A pkg-config file is provided to
       help with this (see doc/plugins.example for details). Note you must
       still rebuild all plugins between minor releases (X.Y).
     * The Windows installers and packages now ship with Qt 5.9.4.

  New Protocol Support

   802.11ax (High Efficiency WLAN (HEW)), ActiveMQ Artemis Core Protocol,
   AMT (Automatic Multicast Tunneling), Bluetooth Mesh, Broadcom tags
   (Broadcom Ethernet switch management frames), CAN-ETH, CVS password
   server, FP Mux, GRPC (gRPC), IEEE 1905.1a, IEEE 802.3br Frame
   Preemption Protocol, ISOBUS, LoRaTap, LoRaWAN, Lustre Filesystem,
   Lustre Network, Network Functional Application Platform Interface
   (NFAPI) Protocol, New Radio Radio Resource Control protocol, NXP
   802.15.4 Sniffer Protocol, PFCP (Packet Forwarding Control Protocol),
   Protobuf (Protocol Buffers), QUIC (IETF), Session Multiplex Protocol,
   SolarEdge monitoring protocol, Tibia, TWAMP and OWAMP, and Wi-Fi Device
   Provisioning Protocol

  Updated Protocol Support

   Too many protocols have been updated to list here.

  New and Updated Capture File Support

   Microsoft Network Monitor

  New and Updated Capture Interfaces support

   LoRaTap
     __________________________________________________________________

Getting Wireshark

   Wireshark source code and installation packages are available from
   [1]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 [2]download page 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.
     __________________________________________________________________

Known Problems

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

   The BER dissector might infinitely loop. ([4]Bug 1516)

   Capture filters aren't applied when capturing from named pipes. ([5]Bug
   1814)

   Filtering tshark captures with read filters (-R) no longer works.
   ([6]Bug 2234)

   Application crash when changing real-time option. ([7]Bug 4035)

   Wireshark and TShark will display incorrect delta times in some cases.
   ([8]Bug 4985)

   Wireshark should let you work with multiple capture files. ([9]Bug
   10488)
     __________________________________________________________________

Getting Help

   Community support is available on [10]Wireshark's Q&A site and on the
   wireshark-users mailing list. Subscription information and archives for
   all of Wireshark's mailing lists can be found on [11]the web site.

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

Frequently Asked Questions

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

   Last updated 2018-02-06 23:13:11 UTC

References

   1. https://www.wireshark.org/download.html
   2. https://www.wireshark.org/download.html#thirdparty
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  10. https://ask.wireshark.org/
  11. https://www.wireshark.org/lists/
  12. http://www.wiresharktraining.com/
  13. https://www.wireshark.org/faq.html


Digests

wireshark-2.5.0.tar.xz: 28197388 bytes
SHA256(wireshark-2.5.0.tar.xz)=3da390e6874cb89bf885c284016fddd6db08543ef4c28747a92f95738618bc28
RIPEMD160(wireshark-2.5.0.tar.xz)=e87520ad8416a000139c16d20224842381e827b2
SHA1(wireshark-2.5.0.tar.xz)=cd1113e5ddeafa2ff3ab181799c07b29d7739907

Wireshark-win64-2.5.0.exe: 59702384 bytes
SHA256(Wireshark-win64-2.5.0.exe)=670c230c8ed7881410f3f2a2d8e962677d1ad12ef0c1c565d73c7ff75c53a6ea
RIPEMD160(Wireshark-win64-2.5.0.exe)=eb454c8ea8c91f0544661913e429157a56b7cea6
SHA1(Wireshark-win64-2.5.0.exe)=da75c56fddef9f24d8c0554f778ec07fdbb65bf8

Wireshark-win32-2.5.0.exe: 54075152 bytes
SHA256(Wireshark-win32-2.5.0.exe)=ad7727e01f537ff59181dbf78e730a75130ecda0597d7e78401a8c7e955b616d
RIPEMD160(Wireshark-win32-2.5.0.exe)=694e3c2fe85e2399e7eddfeccce68598443beb0d
SHA1(Wireshark-win32-2.5.0.exe)=671d712656d4cb43f4f0f613ad6080af7d9fe94e

Wireshark-win32-2.5.0.msi: 43638784 bytes
SHA256(Wireshark-win32-2.5.0.msi)=ba5cc8ab858b889e497df450e952df5165dc9899c1ff0210d14ddedb9a8a1f4c
RIPEMD160(Wireshark-win32-2.5.0.msi)=e250769757e6d1d0eb0c1280fc9bd812857455b3
SHA1(Wireshark-win32-2.5.0.msi)=63a64e6357a48fb482ac40776decfb15eac534d5

Wireshark-win64-2.5.0.msi: 49111040 bytes
SHA256(Wireshark-win64-2.5.0.msi)=eaf45fd9b70441a9389167a462d13c8dfab48d7d6e55d41e7e7b16cc1a560452
RIPEMD160(Wireshark-win64-2.5.0.msi)=74511931c3a736059cfef73fe78b1fd4731c7fdc
SHA1(Wireshark-win64-2.5.0.msi)=33e8f0c45b982c12305f19acfa7197309e45c166

WiresharkPortable_2.5.0.paf.exe: 37437600 bytes
SHA256(WiresharkPortable_2.5.0.paf.exe)=12575310b633b046d65d04ffee1f8fd904c84b3b84fca589c2d42de468ca5c93
RIPEMD160(WiresharkPortable_2.5.0.paf.exe)=2ef87ae80902a8a2ad99c8c6bf6d93fe19e4d589
SHA1(WiresharkPortable_2.5.0.paf.exe)=885a54d73ec4e4e5a13fcf97e8f891d905e8d777

Wireshark 2.5.0 Intel 64.dmg: 35713985 bytes
SHA256(Wireshark 2.5.0 Intel
64.dmg)=47eeb165b6b0975a436a4e9a75be1294b4f5b87970aa0596459c3b29e4b35b71
RIPEMD160(Wireshark 2.5.0 Intel
64.dmg)=8ca73fec21d2cede379647223b544098a0711193
SHA1(Wireshark 2.5.0 Intel 64.dmg)=3b2bacf3296056ba76720afc2ef94d4b3f03e483

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