2019-02-14 23:23:05 +00:00
include::attributes.adoc[]
2018-02-20 01:13:08 +00:00
:stylesheet: ws.css
2018-02-25 17:17:14 +00:00
:linkcss:
2016-11-01 21:35:29 +00:00
2016-07-16 07:53:37 +00:00
= Wireshark {wireshark-version} Release Notes
2018-02-06 20:35:21 +00:00
// Asciidoctor Syntax Quick Reference:
2019-07-20 15:13:59 +00:00
// https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/
2014-04-15 16:31:24 +00:00
2019-12-18 18:29:53 +00:00
This is an experimental release intended to test new features for Wireshark 3.4.
2013-03-15 01:33:46 +00:00
== What is Wireshark?
2019-12-18 18:29:53 +00:00
Wireshark is the world’
It is used for troubleshooting, analysis, development and education.
2013-03-15 01:33:46 +00:00
2018-02-04 23:15:02 +00:00
== What’
2013-03-15 01:33:46 +00:00
2019-12-18 18:29:53 +00:00
Many improvements have been made.
See the “New and Updated Features” section below for more details.
2017-09-02 23:42:00 +00:00
2019-02-06 19:33:12 +00:00
// === Bug Fixes
2013-03-15 01:33:46 +00:00
2019-02-06 19:33:12 +00:00
// The following bugs have been fixed:
2013-03-15 01:33:46 +00:00
2018-05-24 18:35:45 +00:00
//* wsbuglink:5000[]
//* wsbuglink:6000[Wireshark bug]
//* cveidlink:2014-2486[]
2019-11-20 22:55:57 +00:00
//* Wireshark exposed details your sordid redneck past, which were subsequently widely dissemenated on social media.
2018-03-12 15:49:12 +00:00
2013-03-15 01:33:46 +00:00
=== New and Updated Features
2019-11-18 20:10:21 +00:00
The following features are new (or have been significantly updated)
2019-11-20 22:55:57 +00:00
since version 3.2.0:
2019-11-18 20:10:21 +00:00
2019-11-20 22:55:57 +00:00
* Windows executables and installers 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 only].
2019-11-21 14:08:16 +00:00
* Save RTP stream to .au supports any codec with 8000 Hz rate supported by Wireshark (shown in RTP player). If save of audio is not possible (unsupported codec or rate), silence of same length is saved and warning is shown.
2019-11-22 19:16:36 +00:00
* C-ares is now a required dependency.
2019-11-17 12:25:15 +00:00
* Protobuf fields can be dissected as wireshark (header) fields that allows user input
the full names of Protobuf fields or messages in Filter toolbar for searching.
* Dissector based on Protobuf can register itself to a new 'protobuf_field' dissector table,
which is keyed with the full names of fields, for further parsing fields of BYETS or STRING type.
2019-11-18 22:55:25 +00:00
* Wireshark is able to decode, play and save iLBC payload on platforms where iLBC library (https://github.com/TimothyGu/libilbc) is available.
2018-12-13 00:39:20 +00:00
2019-02-06 19:33:12 +00:00
// === Removed Features and Support
2018-05-10 15:53:42 +00:00
2014-06-06 18:39:55 +00:00
//=== Removed Dissectors
2014-01-03 09:48:53 +00:00
2019-02-06 19:33:12 +00:00
// === New File Format Decoding Support
2018-12-11 23:17:53 +00:00
2019-02-06 19:33:12 +00:00
// [commaize]
// --
// --
2014-01-03 09:48:53 +00:00
2013-03-15 01:33:46 +00:00
=== New Protocol Support
2016-06-03 16:21:21 +00:00
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.
2019-11-05 03:21:10 +00:00
Cisco MisCabling Protocol (MCP)
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]
--
2018-05-28 13:16:35 +00:00
--
2013-03-15 01:33:46 +00:00
=== Updated Protocol Support
2016-08-16 14:50:37 +00:00
Too many protocols have been updated to list here.
2013-03-15 01:33:46 +00:00
=== New and Updated Capture File Support
2019-07-24 21:29:13 +00:00
// 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]
2018-08-27 15:17:32 +00:00
--
--
2013-03-15 01:33:46 +00:00
2019-02-06 19:33:12 +00:00
// === New and Updated Capture Interfaces support
2015-04-08 14:09:03 +00:00
2018-01-06 01:02:57 +00:00
//_Non-empty section placeholder._
2018-10-01 17:20:38 +00:00
2019-02-06 19:33:12 +00:00
// === Major API Changes
2014-02-22 19:16:44 +00:00
2013-03-15 01:33:46 +00:00
== Getting Wireshark
Wireshark source code and installation packages are available from
2014-09-17 00:15:56 +00:00
https://www.wireshark.org/download.html.
2013-03-15 01:33:46 +00:00
=== 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
2014-09-17 00:15:56 +00:00
on the https://www.wireshark.org/download.html#thirdparty[download page]
2013-03-15 01:33:46 +00:00
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
2018-08-09 15:43:47 +00:00
The User’
found at https://www.wireshark.org/docs/
2018-02-04 23:15:02 +00:00
Community support is available on https://ask.wireshark.org/[Wireshark’
2013-03-15 01:33:46 +00:00
Q&A site] and on the wireshark-users mailing list. Subscription
2018-02-04 23:15:02 +00:00
information and archives for all of Wireshark’
2014-09-17 00:15:56 +00:00
found on https://www.wireshark.org/lists/[the web site].
2013-03-15 01:33:46 +00:00
2018-08-09 15:43:47 +00:00
Bugs and feature requests can be reported on
https://bugs.wireshark.org/[the bug tracker].
2019-11-20 22:55:57 +00:00
// Official Wireshark training and certification are available from
// https://www.wiresharktraining.com/[Wireshark University].
2013-03-15 01:33:46 +00:00
== Frequently Asked Questions
A complete FAQ is available on the
2014-09-17 00:15:56 +00:00
https://www.wireshark.org/faq.html[Wireshark web site].
