Wireshark-dev: [Wireshark-dev] Wireshark 2.0.10 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Mon, 23 Jan 2017 14:54:53 -0800
I'm proud to announce the release of Wireshark 2.0.10.
__________________________________________________________________
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
Bug Fixes
The following vulnerabilities have been fixed:
The following bugs have been fixed:
* Duplicated Interfaces instances while refreshing. ([1]Bug 11553)
* Time zone name needs to be converted to UTF-8 on Windows. ([2]Bug
11785)
* Crash on fast local interface changes. ([3]Bug 12263)
* SMTP BDAT dissector not reverting to command-code after DATA.
([4]Bug 13030)
* Wireshark fails to recognize V6 DBS Etherwatch capture files.
([5]Bug 13093)
* PPP BCP BPDU size reports not header size, but all data underneath
and its header size in UI. ([6]Bug 13188)
* Uninitialized memcmp on data in daintree-sna.c. ([7]Bug 13246)
* UDLD flags are at other end of octet. ([8]Bug 13280)
* MS-WSP dissector no longer works since commit
8c2fa5b5cf789e6d0d19cd0dd34479d0203d177a. ([9]Bug 13299)
* TBCD string decoded wrongly in MAP ATI message. ([10]Bug 13316)
* Filter Documentation: The tilde (~) operator is not documented.
([11]Bug 13320)
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
DVB-CI, GSM MAP, ISAKMP, MS-WSP, PPP, QUIC, SMTP, and UDLD
New and Updated Capture File Support
There is no new or updated capture file support in this release.
Daintree SNA, and DBS Etherwatch
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
[12]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 [13]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. ([14]Bug 1419)
The BER dissector might infinitely loop. ([15]Bug 1516)
Capture filters aren't applied when capturing from named pipes.
([16]Bug 1814)
Filtering tshark captures with read filters (-R) no longer works.
([17]Bug 2234)
Application crash when changing real-time option. ([18]Bug 4035)
Wireshark and TShark will display incorrect delta times in some cases.
([19]Bug 4985)
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 2017-01-23 20:21:22 UTC
References
1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11553
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11785
3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12263
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13030
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13093
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13188
7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13246
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13280
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13299
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13316
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13320
12. https://www.wireshark.org/download.html
13. https://www.wireshark.org/download.html#thirdparty
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
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.10.tar.bz2: 31209704 bytes
SHA256(wireshark-2.0.10.tar.bz2)=28c3ffcc20b5f80e655bb6408f2aefa8740e9fba3ce84b7cbd4b5001f3886fa8
RIPEMD160(wireshark-2.0.10.tar.bz2)=142de1e809a02460de797fb03ab990daa017c141
SHA1(wireshark-2.0.10.tar.bz2)=dea5241c550ede8a7782ffdbbf479c8603b2e5cd
MD5(wireshark-2.0.10.tar.bz2)=5598b1cea999ffe19038b36cb4a56c7f
Wireshark-win64-2.0.10.exe: 47780784 bytes
SHA256(Wireshark-win64-2.0.10.exe)=e2d7819e2ae8413a6782acd012b3f77f45a199412c734f1358f71809f9d1c1d6
RIPEMD160(Wireshark-win64-2.0.10.exe)=7507d9da169edf70049972713135be0235f863f2
SHA1(Wireshark-win64-2.0.10.exe)=53be62c88bb4c0479bbfabd6367b91df23274254
MD5(Wireshark-win64-2.0.10.exe)=ab13ca204658a84759f0918985fefca9
Wireshark-win32-2.0.10.exe: 44170128 bytes
SHA256(Wireshark-win32-2.0.10.exe)=c324d910c5aa568da392a276ffa8abba0e1452029a3ede33f71b4036f8b958ee
RIPEMD160(Wireshark-win32-2.0.10.exe)=b949cb34a25072bdb09e6875aa9c934487cbdfc8
SHA1(Wireshark-win32-2.0.10.exe)=f4fabbabbb4331c822dc89807683b4febc040151
MD5(Wireshark-win32-2.0.10.exe)=a53e5ff37a76056d1dfb36cd643822de
WiresharkPortable_2.0.10.paf.exe: 43800488 bytes
SHA256(WiresharkPortable_2.0.10.paf.exe)=2d22ce626e1a37dc6d3a3da52be99d1850b855ce3e07676525447e6091d0d62a
RIPEMD160(WiresharkPortable_2.0.10.paf.exe)=5ff600ad56d996122d7aa7ade7b873217b3e4ab4
SHA1(WiresharkPortable_2.0.10.paf.exe)=3e67a6e90e769d75e332ab84890b19662252100b
MD5(WiresharkPortable_2.0.10.paf.exe)=7c03cd1d192a50ef257c74d0602f3592
Wireshark 2.0.10 Intel 64.dmg: 31750800 bytes
SHA256(Wireshark 2.0.10 Intel
64.dmg)=7ae0079b63a6c64eafca253452d2b71d017c7436e61ab7a2a5404c0e6064e69d
RIPEMD160(Wireshark 2.0.10 Intel
64.dmg)=b0e4b585155c3ec93eda5ed1f746579c18cd5517
SHA1(Wireshark 2.0.10 Intel 64.dmg)=39f72e98731c0286350e6ba44ed0d95e19f03a0e
MD5(Wireshark 2.0.10 Intel 64.dmg)=4f8b95b9c40518bc4db0e2e945d11643
Wireshark 2.0.10 Intel 32.dmg: 32490466 bytes
SHA256(Wireshark 2.0.10 Intel
32.dmg)=eb44b9265cc39ca9dc90e9eb86ac5f844be695d86432d859d48417d41bbe0f98
RIPEMD160(Wireshark 2.0.10 Intel
32.dmg)=7de0c6a7e46be5ef780f7784aa9e70e2b7e75814
SHA1(Wireshark 2.0.10 Intel 32.dmg)=c67e5305641959699cbfdcda88897da6d79bea25
MD5(Wireshark 2.0.10 Intel 32.dmg)=0801ab54be0c180c55c28ab72172032c
Attachment:
signature.asc
Description: OpenPGP digital signature
- Prev by Date: Re: [Wireshark-dev] Bugzilla SSL Issue?
- Next by Date: [Wireshark-dev] Wireshark 2.2.4 is now available
- Previous by thread: Re: [Wireshark-dev] Bugzilla SSL Issue?
- Next by thread: [Wireshark-dev] Wireshark 2.2.4 is now available
- Index(es):