Wireshark-announce: [Wireshark-announce] Wireshark 2.0.7 is now available
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Tue, 4 Oct 2016 13:50:52 -0700
I'm proud to announce the release of Wireshark 2.0.7.
__________________________________________________________________
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
* Invalid coloring rules are now disabled instead of discarded. This
will provide forward compatibility with a coloring rule change in
Wireshark 2.2.
Bug Fixes
The following bugs have been fixed:
* Capture File Properties under Statistics Grayed Out after Stopping
a Capture. ([1]Bug 12071)
* Qt: Hidden columns displayed during live capture. ([2]Bug 12377)
* Bad description for NBSS error code 0x81. ([3]Bug 12835)
* Export packet dissections Option disabled after capturing traffic.
([4]Bug 12898)
* TLS padding extension dissector length parsing bug. ([5]Bug 12922)
* Diameter dictionary bugs. ([6]Bug 12927)
* Multiple PortableApps instances can once again be run at the same
time.
New and Updated Features
There are no new features in this release.
New File Format Decoding Support
There are no new file formats in this release.
New Protocol Support
There are no new protocols in this release.
Updated Protocol Support
6LowPAN, DCOM IRemUnknown, Diameter, NBT, NCP, NetFlow, and SSL / TLS
New and Updated Capture File Support
New and Updated Capture Interfaces support
There are no new or updated capture interfaces supported in this
release.
__________________________________________________________________
Getting Wireshark
Wireshark source code and installation packages are available from
[7]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 [8]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.
__________________________________________________________________
Known Problems
Dumpcap might not quit if Wireshark or TShark crashes. ([9]Bug 1419)
The BER dissector might infinitely loop. ([10]Bug 1516)
Capture filters aren't applied when capturing from named pipes.
([11]Bug 1814)
Filtering tshark captures with read filters (-R) no longer works.
([12]Bug 2234)
Resolving ([13]Bug 9044) reopens ([14]Bug 3528) so that Wireshark no
longer automatically decodes gzip data when following a TCP stream.
Application crash when changing real-time option. ([15]Bug 4035)
Hex pane display issue after startup. ([16]Bug 4056)
Packet list rows are oversized. ([17]Bug 4357)
Wireshark and TShark will display incorrect delta times in some cases.
([18]Bug 4985)
The 64-bit version of Wireshark will leak memory on Windows when the
display depth is set to 16 bits ([19]Bug 9914)
Wireshark should let you work with multiple capture files. ([20]Bug
10488)
Dell Backup and Recovery (DBAR) makes many Windows applications crash,
including Wireshark. ([21]Bug 12036)
__________________________________________________________________
Getting Help
Community support is available on [22]Wireshark's Q&A site and on the
wireshark-users mailing list. Subscription information and archives for
all of Wireshark's mailing lists can be found on [23]the web site.
Official Wireshark training and certification are available from
[24]Wireshark University.
__________________________________________________________________
Frequently Asked Questions
A complete FAQ is available on the [25]Wireshark web site.
__________________________________________________________________
Last updated 2016-10-04 17:19:54 UTC
References
1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12071
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12377
3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12835
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12898
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12922
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12927
7. https://www.wireshark.org/download.html
8. https://www.wireshark.org/download.html#thirdparty
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3528
15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056
17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9914
20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12036
22. https://ask.wireshark.org/
23. https://www.wireshark.org/lists/
24. http://www.wiresharktraining.com/
25. https://www.wireshark.org/faq.html
Digests
wireshark-2.0.7.tar.bz2: 31194949 bytes
SHA256(wireshark-2.0.7.tar.bz2)=e7d161e147679fb0a2bf81efe7297988fd908155b9835cb0825083afae89e6d4
RIPEMD160(wireshark-2.0.7.tar.bz2)=c6336bd904391e060b3ab7768545605b70bffa81
SHA1(wireshark-2.0.7.tar.bz2)=6825e8dd2ff9e6f89f0c93c4f15ea39263df1633
MD5(wireshark-2.0.7.tar.bz2)=556c36086539541c1ce60102e6a10a2e
Wireshark-win32-2.0.7.exe: 44007576 bytes
SHA256(Wireshark-win32-2.0.7.exe)=eecc897c0fba89baa260723910b4512a154a1e84bde1da76f0de1f441fb2205b
RIPEMD160(Wireshark-win32-2.0.7.exe)=c94b74deeb2bc5132b52d6bf6dbfb380fa27fe88
SHA1(Wireshark-win32-2.0.7.exe)=759dfbca2a04aeb84e435c881e11b19defc31989
MD5(Wireshark-win32-2.0.7.exe)=a335ccfc22c46d15211e2cff9b691d67
Wireshark-win64-2.0.7.exe: 47643232 bytes
SHA256(Wireshark-win64-2.0.7.exe)=9c1eadf52f5632ebb658d6f41a72064f407cd6096ac2e5a8b04f15870bac8a4f
RIPEMD160(Wireshark-win64-2.0.7.exe)=49aaa61e3cb338739b09c38ef462d22cf18f207f
SHA1(Wireshark-win64-2.0.7.exe)=0982d6a968032c3c852930c0a627c6f58082e7ef
MD5(Wireshark-win64-2.0.7.exe)=5015353a1c3762fbf982189c5267dab5
WiresharkPortable_2.0.7.paf.exe: 43668392 bytes
SHA256(WiresharkPortable_2.0.7.paf.exe)=9807153cb57cd2dcd440ca535a555eeadd11b13ee8dc8664d71d26d400f7c3f5
RIPEMD160(WiresharkPortable_2.0.7.paf.exe)=3cf2739fd89ebe2a846cec852661252e0166a684
SHA1(WiresharkPortable_2.0.7.paf.exe)=8b9b7f94a92d5f58cf60ed9b730b28c876fb0f67
MD5(WiresharkPortable_2.0.7.paf.exe)=6c4b8ff2009f05758d5a88596bb06351
Wireshark 2.0.7 Intel 32.dmg: 32444619 bytes
SHA256(Wireshark 2.0.7 Intel
32.dmg)=fc4c50e74dc43f30994faa672eae97f87ee15e53121a65ee40b8ce6635b239a3
RIPEMD160(Wireshark 2.0.7 Intel
32.dmg)=58dae48b9371b08a02581e7302eebf3c74dc5a6f
SHA1(Wireshark 2.0.7 Intel 32.dmg)=01e747a5cf3b9043be200f4278e03668155016d4
MD5(Wireshark 2.0.7 Intel 32.dmg)=103227d9aaa775fe7a74214cfe168758
Wireshark 2.0.7 Intel 64.dmg: 31714605 bytes
SHA256(Wireshark 2.0.7 Intel
64.dmg)=5a0d2c0b83b2c6087c24c9d89b42bed4cd2f2233158b605ea1450c392961096e
RIPEMD160(Wireshark 2.0.7 Intel
64.dmg)=bae5c3348271f30b0e634db88840957d6f7fb943
SHA1(Wireshark 2.0.7 Intel 64.dmg)=310ac609fd94668ffccd43a744b505de0f024ee1
MD5(Wireshark 2.0.7 Intel 64.dmg)=56c439af7290392026d4d4ee2f11dcb3
Attachment:
signature.asc
Description: OpenPGP digital signature
- Prev by Date: [Wireshark-announce] Wireshark 2.2.1 is now available
- Previous by thread: [Wireshark-announce] Wireshark 2.2.1 is now available
- Index(es):