Wireshark-users: [Wireshark-users] Wireshark 1.10.8 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Thu, 12 Jun 2014 15:26:59 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm proud to announce the release of Wireshark 1.10.8.
__________________________________________________________
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.
* [1]wnpa-sec-2014-07
The frame metadissector could crash. ([2]Bug 9999, [3]Bug
10030)
Versions affected: 1.10.0 to 1.10.7
[4]CVE-2014-4020
The following bugs have been fixed:
* VoIP flow graph crash upon opening. ([5]Bug 9179)
* Tshark with "-F pcap" still generates a pcapng file.
([6]Bug 9991)
* IPv6 Next Header 0x3d recognized as SHIM6. ([7]Bug 9995)
* Failed to export pdml on large pcap. ([8]Bug 10081)
* TCAP: set a fence on info column after calling sub
dissector ([9]Bug 10091)
* Dissector bug in JSON protocol. ([10]Bug 10115)
* GSM RLC MAC: do not skip too many lines of the CSN_DESCR
when the field is missing ([11]Bug 10120)
* Wireshark PEEKREMOTE incorrectly decoding QoS data packets
from Cisco Sniffer APs. ([12]Bug 10139)
* IEEE 802.11: fix dissection of HT Capabilities ([13]Bug
10166)
New and Updated Features
There are no new features in this release.
New Protocol Support
There are no new protocols in this release.
Updated Protocol Support
CIP, EtherNet/IP, GSM RLC MAC, IEEE 802.11, IPv6, and TCAP
New and Updated Capture File Support
pcap-ng, and PEEKREMOTE
__________________________________________________________
Getting Wireshark
Wireshark source code and installation packages are available
from [14]http://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 [15]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. ([16]Bug
1419)
The BER dissector might infinitely loop. ([17]Bug 1516)
Capture filters aren't applied when capturing from named pipes.
([18]Bug 1814)
Filtering tshark captures with read filters (-R) no longer
works. ([19]Bug 2234)
The 64-bit Windows installer does not support Kerberos
decryption. ([20]Win64 development page)
Resolving ([21]Bug 9044) reopens ([22]Bug 3528) so that
Wireshark no longer automatically decodes gzip data when
following a TCP stream.
Application crash when changing real-time option. ([23]Bug
4035)
Hex pane display issue after startup. ([24]Bug 4056)
Packet list rows are oversized. ([25]Bug 4357)
Summary pane selected frame highlighting not maintained.
([26]Bug 4445)
Wireshark and TShark will display incorrect delta times in some
cases. ([27]Bug 4985)
__________________________________________________________
Getting Help
Community support is available on [28]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 [29]the web site.
Official Wireshark training and certification are available
from [30]Wireshark University.
__________________________________________________________
Frequently Asked Questions
A complete FAQ is available on the [31]Wireshark web site.
__________________________________________________________
Last updated 2014-06-12 12:30:53 PDT
References
1. https://www.wireshark.org/security/wnpa-sec-2014-07.html
2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9999
3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10030
4. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4020
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9179
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9991
7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9995
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10081
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10091
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10115
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10120
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10139
13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10166
14. http://www.wireshark.org/download.html
15. http://www.wireshark.org/download.html#thirdparty
16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
20. https://wiki.wireshark.org/Development/Win64
21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044
22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3528
23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056
25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445
27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
28. http://ask.wireshark.org/
29. http://www.wireshark.org/lists/
30. http://www.wiresharktraining.com/
31. http://www.wireshark.org/faq.html
Digests
wireshark-1.10.8.tar.bz2: 26715025 bytes
MD5(wireshark-1.10.8.tar.bz2)=510dc3b063785549b41ebc748ac21055
SHA1(wireshark-1.10.8.tar.bz2)=aa6067ce91637506504c8b954caf75ac98742152
RIPEMD160(wireshark-1.10.8.tar.bz2)=5c2aab7477ab2f9b5f966fe5f973ff5619c242f9
Wireshark-win64-1.10.8.exe: 28013520 bytes
MD5(Wireshark-win64-1.10.8.exe)=e256e3e7ae0a68f7e75ab97d859c7db4
SHA1(Wireshark-win64-1.10.8.exe)=067af8281c656a4d12122e3d8a969dff792f73a0
RIPEMD160(Wireshark-win64-1.10.8.exe)=6712fa0cd38126f1c269bcdcb451619ac9ecf975
Wireshark-win32-1.10.8.exe: 22157280 bytes
MD5(Wireshark-win32-1.10.8.exe)=54ff02439cbea9a8634445b7347c579c
SHA1(Wireshark-win32-1.10.8.exe)=08af8ed728b106e9f04d5edd53027498f5bb243b
RIPEMD160(Wireshark-win32-1.10.8.exe)=d654fd7a2c58b5e25460a854ce2bff9316e1d90f
Wireshark-1.10.8.u3p: 30644928 bytes
MD5(Wireshark-1.10.8.u3p)=471e4257f37741c1e46fe6ad672510f4
SHA1(Wireshark-1.10.8.u3p)=52be28ba6e289d747be2c720dcf953887c02f850
RIPEMD160(Wireshark-1.10.8.u3p)=6ddb45bd3a08d21e90be5a2116a9c4739bb23a67
WiresharkPortable-1.10.8.paf.exe: 23526016 bytes
MD5(WiresharkPortable-1.10.8.paf.exe)=2921097f49b3e79b93ae0f26dfca461b
SHA1(WiresharkPortable-1.10.8.paf.exe)=a3477f7bdd8f71241b2c21db11c5581d60c38ea2
RIPEMD160(WiresharkPortable-1.10.8.paf.exe)=3c8994b67a75357669b23dddc4473d0474ddca8c
Wireshark 1.10.8 Intel 32.dmg: 20467272 bytes
MD5(Wireshark 1.10.8 Intel 32.dmg)=5da5d7874e6bef4e581a69b736800763
SHA1(Wireshark 1.10.8 Intel
32.dmg)=53d57f90834d3b3baf3d1382b9d8f2bd6941b121
RIPEMD160(Wireshark 1.10.8 Intel
32.dmg)=7d093cabfff7215ec17e317dfabbaf3ba67bf640
Wireshark 1.10.8 Intel 64.dmg: 24775434 bytes
MD5(Wireshark 1.10.8 Intel 64.dmg)=355c5ebabe825b90fa1abdf4713d9ddb
SHA1(Wireshark 1.10.8 Intel
64.dmg)=830b6535f6f3212f813054851a6baed535303f75
RIPEMD160(Wireshark 1.10.8 Intel
64.dmg)=3e521a3c1ea627bc4f058cd8ebd13444d986ab06
patch-wireshark-1.10.7-to-1.10.8.bz2: 110206 bytes
MD5(patch-wireshark-1.10.7-to-1.10.8.bz2)=aabcd9603bb91fb8c8e1275bab87a123
SHA1(patch-wireshark-1.10.7-to-1.10.8.bz2)=d56411665e1c781a25b84c9c25d6b9f6f1d66661
RIPEMD160(patch-wireshark-1.10.7-to-1.10.8.bz2)=82256d8668087b904cc24c8072da215279e7f03c
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlOaKTMACgkQpw8IXSHylJo3OQCeNpDrleIfwN2soXQyD6pEtcv7
6aYAnjZfRnHuqJAlg4XnzORrDERrD3O3
=gvlq
-----END PGP SIGNATURE-----
- Prev by Date: [Wireshark-users] How can I solve my DHCP problem via Wireshark.
- Next by Date: [Wireshark-users] Wireshark 1.8.15 is now available
- Previous by thread: [Wireshark-users] How can I solve my DHCP problem via Wireshark.
- Next by thread: [Wireshark-users] Wireshark 1.8.15 is now available
- Index(es):