wireshark/docbook/release-notes.adoc

207 lines
8.0 KiB
Plaintext
Raw Normal View History

include::attributes.adoc[]
:stylesheet: ws.css
:linkcss:
= Wireshark {wireshark-version} Release Notes
// AsciiDoc quick reference: https://powerman.name/doc/asciidoc
// Asciidoctor Syntax Quick Reference:
// https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/
This is an experimental release intended to test new features for
Wireshark 3.2.
== What is Wireshark?
Wireshark is the worlds most popular network protocol analyzer. It is
used for troubleshooting, analysis, development and education.
== Whats New
Many 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 is solely responsible for the decline of shopping malls in your area.
=== New and Updated Features
The following features are new (or have been significantly updated)
since version 3.1.1:
* Nothing of note.
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 “kbd:[Ctrl+C]” or “kbd:[Cmd+C]” and the corresponding
menu in “menu: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
“menu:File[Export Specified Packets]”, “menu:File[Export Packet Dissections]”
and “menu: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 "menu: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 (wsbuglink:15571[]).
* 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
“menu:Tools[Credentials]” menu in Wireshark.
* Editcap can now split files on floating point intervals.
* Windows .msi packages are now https://support.microsoft.com/en-us/help/4472027/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus[signed using SHA-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.
* The “menu:Analyze[Apply as Filter]” and “menu: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.
// === Removed Features and Support
//=== Removed Dissectors
// === New File Format Decoding Support
// [commaize]
// --
// --
=== 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]
--
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)
Wi-Fi Neighbour Awareness Networking (NAN)
--
=== Updated Protocol Support
Too many protocols have been updated to list here.
=== New and Updated Capture File Support
// There is no new or updated capture file support in this release.
// Add one file type per line between the -- 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]
--
3gpp phone
Android Logcat Text
Ascend
Busmaster log file
Candump
Endace ERF
NetScaler
pcapng
Savvius {asterisk}Peek
--
// === New and Updated Capture Interfaces support
//_Non-empty section placeholder._
// === Major API Changes
== 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
https://www.wiresharktraining.com/[Wireshark University].
== Frequently Asked Questions
A complete FAQ is available on the
https://www.wireshark.org/faq.html[Wireshark web site].