Wireshark-announce: [Wireshark-announce] Wireshark 2.6.0 is now available
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Tue, 24 Apr 2018 11:51:01 -0700
I'm proud to announce the release of Wireshark 2.6.0.
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
Wireshark 2.6 is the last release that will support the legacy (GTK+)
user interface. It will not be supported or available in Wireshark
3.0.
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:
Dumpcap might not quit if Wireshark or TShark crashes. (Bug 1419[1])
New and Updated Features
The following features are new (or have been significantly updated)
since version 2.5.0:
• HTTP Request sequences are now supported.
• Wireshark now supports MaxMind DB files. Support for GeoIP and
GeoLite Legacy databases has been removed.
• The Windows packages are now built using Microsoft Visual Studio
2017.
• The IP map feature (the “Map” button in the “Endpoints” dialog)
has been removed.
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.
• The generic data dissector can now uncompress zlib compressed
data.
• DNS Stats now supports service level statistics.
• DNS filters for retransmissions and unsolicited responses have
been added.
• The “tcptrace” TCP Stream graph now shows duplicate ACKS and zero
window advertisements.
• The membership operator now supports ranges, allowing display
filters such as tcp.port in {4430..4434} to be expressed. See the
User’s Guide, chapter Building display filter expressions for
details.
New Protocol Support
ActiveMQ Artemis Core Protocol, AMT (Automatic Multicast Tunneling),
AVSP (Arista Vendor Specific Protocol), Bluetooth Mesh, Broadcom tags
(Broadcom Ethernet switch management frames), CAN-ETH, CVS password
server, Excentis DOCSIS31 XRA header, F1 Application Protocol,
F5ethtrailer, FP Mux, GRPC (gRPC), IEEE 1905.1a, IEEE 802.11ax (High
Efficiency WLAN (HEW)), IEEE 802.15.9 IEEE Recommended Practice for
Transport of Key Management Protocol (KMP) Datagrams, IEEE 802.3br
Frame Preemption Protocol, ISOBUS, LoRaTap, LoRaWAN, Lustre
Filesystem, Lustre Network, Nano / RaiBlocks Cryptocurrency Protocol
(UDP), Network Functional Application Platform Interface (NFAPI)
Protocol, New Radio Radio Link Control protocol, New Radio Radio
Resource Control protocol, NR (5G) MAC protocol, NXP 802.15.4 Sniffer
Protocol, Object Security for Constrained RESTful Environments
(OSCORE), PFCP (Packet Forwarding Control Protocol), Protobuf
(Protocol Buffers), QUIC (IETF), RFC 4108 Using CMS to Protect
Firmware Packages, Session Multiplex Protocol, SolarEdge monitoring
protocol, Steam In-Home Streaming Discovery Protocol, Tibia, TWAMP
and OWAMP, Wi-Fi Device Provisioning Protocol, and Wi-SUN FAN
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
https://www.wireshark.org/download.html[2].
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 download page[3] 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
The BER dissector might infinitely loop. (Bug 1516[4])
Capture filters aren’t applied when capturing from named pipes. (Bug
1814[5])
Filtering tshark captures with read filters (-R) no longer works. (Bug
2234[6])
Application crash when changing real-time option. (Bug 4035[7])
Wireshark and TShark will display incorrect delta times in some cases.
(Bug 4985[8])
Wireshark should let you work with multiple capture files. (Bug
10488[9])
Getting Help
Community support is available on Wireshark’s Q&A site[10] and on the
wireshark-users mailing list. Subscription information and archives
for all of Wireshark’s mailing lists can be found on the web site[11].
Official Wireshark training and certification are available from
Wireshark University[12].
Frequently Asked Questions
A complete FAQ is available on the Wireshark web site[13].
Last updated 2018-04-24 17:32:38 UTC
References
1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
2. https://www.wireshark.org/download.html
3. https://www.wireshark.org/download.html#thirdparty
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.6.0.tar.xz: 28314868 bytes
SHA256(wireshark-2.6.0.tar.xz)=711c7f01d27a8817d58277a5487cef3e3c7bab1c8caaf8f4c92aa21015b9117f
RIPEMD160(wireshark-2.6.0.tar.xz)=4eb1a446dabff8f452737ea22bfc341a3be89a3f
SHA1(wireshark-2.6.0.tar.xz)=d1f53751c5b24d6b1695117fb396a6b202e88451
Wireshark-win64-2.6.0.exe: 59943760 bytes
SHA256(Wireshark-win64-2.6.0.exe)=a5c276cd3b2b3023b597debdf292cccb7f7f64400cd40d2ef5dd139d18424936
RIPEMD160(Wireshark-win64-2.6.0.exe)=0b5bd8f1ccd332cce5fe84da4a738015a223d597
SHA1(Wireshark-win64-2.6.0.exe)=c40d1d86fe64a5a25d80b60d51bdb3bcc8bda0e5
Wireshark-win32-2.6.0.exe: 54218808 bytes
SHA256(Wireshark-win32-2.6.0.exe)=d96e76ab9d5d94cb70cd7686ff0302d482a5be79ae8fc95934902de79b9be94b
RIPEMD160(Wireshark-win32-2.6.0.exe)=c8c84d84afa90199f1a54374e31c53a860182c76
SHA1(Wireshark-win32-2.6.0.exe)=3f9444afff971703f0a8c1913ce688cf6a28f205
Wireshark-win64-2.6.0.msi: 49328128 bytes
SHA256(Wireshark-win64-2.6.0.msi)=aa8765c8b398f177ef960e2a936bdb20f21f0df7327fec65098c80f975a601ec
RIPEMD160(Wireshark-win64-2.6.0.msi)=6fde01e3ad151fbdc0c5cbb42e4fc2a4b71a0798
SHA1(Wireshark-win64-2.6.0.msi)=7f1c374bcb54888deaee420335413bea0e0e8f92
Wireshark-win32-2.6.0.msi: 43687936 bytes
SHA256(Wireshark-win32-2.6.0.msi)=e44de9f328657bc68fba991fb1edae905cad579e6d153acc032597acd081c523
RIPEMD160(Wireshark-win32-2.6.0.msi)=51de3c000f9b28907f9ecfb01d6f5fb98be76ab8
SHA1(Wireshark-win32-2.6.0.msi)=4b1ee29fec281170975c05388e1eb2d4ecae0cf9
WiresharkPortable_2.6.0.paf.exe: 37448928 bytes
SHA256(WiresharkPortable_2.6.0.paf.exe)=59a0e2708988222032a5b0dfd30a5e64b11d2c947f70b0d77fd0a1f4890a3c53
RIPEMD160(WiresharkPortable_2.6.0.paf.exe)=e9f627ae37b861f09a80fe4bf88762a118824698
SHA1(WiresharkPortable_2.6.0.paf.exe)=c88b195266620a1a6dee64e11ec4dc9501d5fcba
Wireshark 2.6.0 Intel 64.dmg: 168876995 bytes
SHA256(Wireshark 2.6.0 Intel
64.dmg)=0d20a6075a7c92ed37cefa19ba9ae128d53ed06038c633043b43dd3f0091cd83
RIPEMD160(Wireshark 2.6.0 Intel
64.dmg)=1faa9631276f34de78b3b690751165d5b408faee
SHA1(Wireshark 2.6.0 Intel 64.dmg)=fefc72db0abab71fedd5f1efda3f0e4f11a0a4b1
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
- Prev by Date: [Wireshark-announce] Wireshark 2.2.14 is now available
- Previous by thread: [Wireshark-announce] Wireshark 2.2.14 is now available
- Index(es):