wireshark/docbook/release-notes.adoc

139 lines
4.5 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.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 (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
"tools" menu in Wireshark.
* Editcap can now split files on floating point intervals.
// === 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]
--
evolved Common Public Radio Interface (eCPRI)
Distributed Replicated Block Device (DRBD)
GSM/3GPP CBSP (Cell Broadcast Service Protocol)
NVM Express over Fabrics for TCP (nvme-tcp)
Graylog Extended Log Format over UDP (GELF)
FTDI FT USB Bridging Devices (FTDI FT)
CableLabs Layer-3 Protocol IEEE EtherType 0xb4e3 (CL3)
Dual Channel Wi-Fi (CL3DCW)
NR Positioning Protocol A (NRPPa) TS 38.455
Network Controller Sideband Interface (NCSI)
--
=== 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]
--
--
// === 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].