wireshark/docbook/release-notes.asciidoc

235 lines
8.8 KiB
Plaintext
Raw Normal View History

include::attributes.asciidoc[]
:stylesheet: ws.css
:linkcss:
= Wireshark {wireshark-version} Release Notes
// AsciiDoc quick reference: http://powerman.name/doc/asciidoc
// Asciidoctor Syntax Quick Reference:
// http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/
This is an experimental release intended to test new features for
Wireshark 3.0.
== What is Wireshark?
Wireshark is the worlds most popular network protocol analyzer. It is
used for troubleshooting, analysis, development and education.
== Whats 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:
//* wsbuglink:5000[]
//* wsbuglink:6000[Wireshark bug]
//* cveidlink:2014-2486[]
//* Wireshark slowly leaked water under the kitchen sink over the course of several months, causing a big mess.
* Data following a TCP ZeroWindowProbe is marked as retransmission and not passed to subdissectors (wsbuglink:15427[])
//_Non-empty section placeholder._
Text and Image columns were handled incorrectly for TDS 7.0 and 7.1. (wsbuglink:3098[])
Dumpcap might not quit if Wireshark or TShark crashes.
(wsbuglink:1419[])
=== New and Updated Features
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 (wsbuglink:15163[]).
* 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 (wsbuglink:12004[]).
* The Ethernet and IEEE 802.11 dissectors no longer validate the frame check sequence (checksum) by default.
tcp: add support for reassembling out-of-order segments Currently out-of-order segments will result in cutting a stream into two pieces while the out-of-order segment itself is ignored. For example, a stream of segments "ABDCE" is interpreted as "AB", "DE" with "C" ignored. This behavior breaks TLS decryption or prevent application layer PDUs (such as HTTP requests/responses) from being reconstructed. To fix this, buffer segments when a gap is detected. The proposed approach extends the "multi-segment PDU" (MSP) mechanism which is normally used for linking multiple, sequential TCP segments into a single PDU. When a gap is detected between segments, it is assumed that the segments within this gap are out-of-order and will be received (or retransmitted) later. The current implementation has a limitation though, if multiple gaps exist, then the subdissector will only be called when all gaps are filled (the subdissector will receive segments later than necessary). For example with "ACEBD", "ABC" can already be processed after "B" is received (with "E" still buffered), but due to how MSP are extended, it must receive "D" too before it reassembles "ABCDE". In practice this could mean that the request/response times between HTTP requests and responses are slightly off, but at least the stream is correct now. (These limitations are documented in the User's Guide.) As the feature fails at least the 802.11 decryption test where packets are missing (instead of OoO), hide this feature behind a preference. Tested with captures containing out-of-order TCP segments from the linked bug reports, comparing the effect of toggling the preference on the summary output of tshark, the verbose output (-V) and the two-pass output (-2 or -2V). Captures marked with "ok" just needed "simple" out-of-order handling. Captures marked with "ok2" additionally required the reassembly API change to set the correct reassembled length. This change does "regress" on bug 10289 though when the preference is enabled as retransmitted single-segment PDUs are now passed to subdissectors. I added a TODO comment for this unrelated cosmetic issue. Bug: 3389 # capture 2907 (HTTP) ok Bug: 4727 # capture 4590 (HTTP) ok Bug: 9461 # capture 12130 (TLS/HTTP/RPC-over-HTTP +key 12131) ok Bug: 12006 # capture 14236 (HTTP) ok2; capture 15261 (HTTP) ok Bug: 13517 # capture 15370 (HTTP) ok; capture 16059 (MQ) ok Bug: 13754 # capture 15593 (MySQL) ok2 Bug: 14649 # capture 16305 (WebSocket) ok Change-Id: If3938c5c1c96db8f7f50e39ea779f623ce657d56 Reviewed-on: https://code.wireshark.org/review/27943 Petri-Dish: Peter Wu <peter@lekensteyn.nl> Tested-by: Petri Dish Buildbot Reviewed-by: Anders Broman <a.broman58@gmail.com>
2018-06-01 13:11:47 +00:00
* 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 Users Guide, chapter _TCP Reassembly_ for details.
* Decryption support for the new WireGuard dissector (wsbuglink:15011[], 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 (wsbuglink:15252[]).
* 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.
* TSharks `-z compare` option was removed.
* Building with Cygwin is no longer supported on Windows.
//=== Removed Dissectors
=== New File Format Decoding Support
[commaize]
--
Ruby Marshal format
--
=== New Protocol Support
Switch from AsciiDoc to Asciidoctor. Switch the markup text processor for files in the docbook directory from AsciiDoc to Asciidoctor. Asciidoctor has several useful features (such as direct PDF output) and is actively developed. It's written in Ruby but that dependency can be sidestepped with AsciidoctorJ, a self-contained bundle that only depends on the JRE. The current toolchain targets require Python, AsciiDoc, DocBook XML, DocBook XSL, Java, FOP, xsltproc, lynx, and the HTMLHelp compiler: HTML: AsciiDoc → DocBook XML → xsltproc + DocBook XSL Chunked HTML: AsciiDoc → DocBook XML → xsltproc + DocBook XSL PDF: AsciiDoc → DocBook XML → xsltproc + DocBook XSL → FOP HTMLHelp: AsciiDoc → DocBook XML → xsltproc + DocBook XSL → HHC This change removes the AsciiDoc and FOP requirements and adds either AsciidoctorJ or Asciidoctor + Ruby: HTML: Asciidoctor → DocBook XML → xsltproc + DocBook XSL Chunked HTML: Asciidoctor → DocBook XML → xsltproc + DocBook XSL PDF: Asciidoctor HTMLHelp: Asciidoctor → DocBook XML → xsltproc + DocBook XSL → HHC Ideally we could generate all of these using AsciidoctorJ, Java, and lynx. Unfortunately we're not there yet. The release notes depend on several macros (ws-buglink, ws-salink, cve-idlink, sort-and-group). Add Asciidoctor (Ruby) equivalents. Remove the BUILD_xxx_GUIDES CMake options and add various output targets automatically. This means that you have to build the various documentation targets explicitly. Change-Id: I31930677a656b99b1c6839bb6c33a13db951eb9a Reviewed-on: https://code.wireshark.org/review/25668 Petri-Dish: Gerald Combs <gerald@wireshark.org> Tested-by: Petri Dish Buildbot Reviewed-by: Gerald Combs <gerald@wireshark.org>
2017-10-19 22:03:55 +00:00
// Add one protocol per line between the -- delimiters.
[commaize]
--
Apple Wireless Direct Link (AWDL)
GeoNetworking, BTP dissectors (ITS-V2X) Implements V2X protocol dissectors: * Geonetworking (network layer): Dissector is registered on top of Ethernet (ethertype=0x8947). Secured Packets are dissected up to the basic header, the rest is shown as data. GN_ADDR address type is registerd and provides resolution of station type and country code in the address. MID is shown as an ethernet address. All the fields are dissected for non Secured Packets. A subdissector table named "geonw.ch.nh" is provided on the next header field. IPv6 is automatically registered. Heuristic dissectors is not supported. If no dissector is foundd, payload is shown as data. A preference boolean allows to enable/disable sequence number checking. Tap "geonw" gets headers of all packets (with most fields). Expert info tests if and provide feedback on: - version is zero (no other version possible), - reserved fields are zeros, - payload_len matching with reported length of buffer, - Remaining Hop Limit is 1 for Beacon and SHB, - low RHL or RHL > Max Hop Limit, - country code is less than 999 (3 digits ITU-T E.164), - latitude, longitude, heading and angle limits, - (suspected) duplicate packets, - LS_REQUEST/LS_REPLY matching. * Basic Transport Portocol: BTP-X (X=A or B) dissectors are registered on top of Geonetworking. Subdissector tables "btpx.port" allow to register for a given port, while heuristic dissector can register to "btpx.payload". Decode as capability is supported. "btpx" taps get headers of all packets with ports/@ infos. "btpx_follow" taps get the payload. Bug: 15148 Change-Id: Iab5f4486d4c38068d9ad4361e77296b747f9b1bb Reviewed-on: https://code.wireshark.org/review/30992 Petri-Dish: Anders Broman <a.broman58@gmail.com> Tested-by: Petri Dish Buildbot Reviewed-by: Anders Broman <a.broman58@gmail.com>
2018-12-13 15:43:33 +00:00
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)
Elektrobit High Speed Capture Replay (EBHSCR)
EVS (3GPP TS 26.445 A.2 EVS RTP)
Exablaze trailers
Great Britain Companion Specification (GBCS) used in the Smart Metering Equipment Technical Specifications (SMETS)
General Circuit Services Notification Application Protocol (GCSNA)
GeoNetworking, BTP dissectors (ITS-V2X) Implements V2X protocol dissectors: * Geonetworking (network layer): Dissector is registered on top of Ethernet (ethertype=0x8947). Secured Packets are dissected up to the basic header, the rest is shown as data. GN_ADDR address type is registerd and provides resolution of station type and country code in the address. MID is shown as an ethernet address. All the fields are dissected for non Secured Packets. A subdissector table named "geonw.ch.nh" is provided on the next header field. IPv6 is automatically registered. Heuristic dissectors is not supported. If no dissector is foundd, payload is shown as data. A preference boolean allows to enable/disable sequence number checking. Tap "geonw" gets headers of all packets (with most fields). Expert info tests if and provide feedback on: - version is zero (no other version possible), - reserved fields are zeros, - payload_len matching with reported length of buffer, - Remaining Hop Limit is 1 for Beacon and SHB, - low RHL or RHL > Max Hop Limit, - country code is less than 999 (3 digits ITU-T E.164), - latitude, longitude, heading and angle limits, - (suspected) duplicate packets, - LS_REQUEST/LS_REPLY matching. * Basic Transport Portocol: BTP-X (X=A or B) dissectors are registered on top of Geonetworking. Subdissector tables "btpx.port" allow to register for a given port, while heuristic dissector can register to "btpx.payload". Decode as capability is supported. "btpx" taps get headers of all packets with ports/@ infos. "btpx_follow" taps get the payload. Bug: 15148 Change-Id: Iab5f4486d4c38068d9ad4361e77296b747f9b1bb Reviewed-on: https://code.wireshark.org/review/30992 Petri-Dish: Anders Broman <a.broman58@gmail.com> Tested-by: Petri Dish Buildbot Reviewed-by: Anders Broman <a.broman58@gmail.com>
2018-12-13 15:43:33 +00:00
GeoNetworking (GeoNw)
GLOW Lawo Emberplus Data format
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)
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)
Z39.50 Information Retrieval Protocol
PCOM protocol
--
=== Updated Protocol Support
Too many protocols have been updated to list here.
=== New and Updated Capture File Support
//_Non-empty section placeholder._
// Add one file type per line between the --sort-and-group-- delimiters.
Switch from AsciiDoc to Asciidoctor. Switch the markup text processor for files in the docbook directory from AsciiDoc to Asciidoctor. Asciidoctor has several useful features (such as direct PDF output) and is actively developed. It's written in Ruby but that dependency can be sidestepped with AsciidoctorJ, a self-contained bundle that only depends on the JRE. The current toolchain targets require Python, AsciiDoc, DocBook XML, DocBook XSL, Java, FOP, xsltproc, lynx, and the HTMLHelp compiler: HTML: AsciiDoc → DocBook XML → xsltproc + DocBook XSL Chunked HTML: AsciiDoc → DocBook XML → xsltproc + DocBook XSL PDF: AsciiDoc → DocBook XML → xsltproc + DocBook XSL → FOP HTMLHelp: AsciiDoc → DocBook XML → xsltproc + DocBook XSL → HHC This change removes the AsciiDoc and FOP requirements and adds either AsciidoctorJ or Asciidoctor + Ruby: HTML: Asciidoctor → DocBook XML → xsltproc + DocBook XSL Chunked HTML: Asciidoctor → DocBook XML → xsltproc + DocBook XSL PDF: Asciidoctor HTMLHelp: Asciidoctor → DocBook XML → xsltproc + DocBook XSL → HHC Ideally we could generate all of these using AsciidoctorJ, Java, and lynx. Unfortunately we're not there yet. The release notes depend on several macros (ws-buglink, ws-salink, cve-idlink, sort-and-group). Add Asciidoctor (Ruby) equivalents. Remove the BUILD_xxx_GUIDES CMake options and add various output targets automatically. This means that you have to build the various documentation targets explicitly. Change-Id: I31930677a656b99b1c6839bb6c33a13db951eb9a Reviewed-on: https://code.wireshark.org/review/25668 Petri-Dish: Gerald Combs <gerald@wireshark.org> Tested-by: Petri Dish Buildbot Reviewed-by: Gerald Combs <gerald@wireshark.org>
2017-10-19 22:03:55 +00:00
[commaize]
--
RFC 7468 (PEM)
Ruby marshal object files
systemd Journal Export
Unigraf DPA-400 DisplayPort AUX channel monitor
--
=== New and Updated Capture Interfaces support
//_Non-empty section placeholder._
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. (wsbuglink:15118[])
== 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 https://www.wireshark.org/download.html#thirdparty[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.
== Getting Help
The Users Guide, manual pages and various other documentation can be
found at https://www.wireshark.org/docs/
Community support is available on https://ask.wireshark.org/[Wiresharks
Q&A site] and on the wireshark-users mailing list. Subscription
information and archives for all of Wiresharks mailing lists can be
found on https://www.wireshark.org/lists/[the web site].
Bugs and feature requests can be reported on
https://bugs.wireshark.org/[the bug tracker].
Official Wireshark training and certification are available from
http://www.wiresharktraining.com/[Wireshark University].
== Frequently Asked Questions
A complete FAQ is available on the
https://www.wireshark.org/faq.html[Wireshark web site].