Wireshark-dev: [Wireshark-dev] Wireshark 1.6.8 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 22 May 2012 11:13:12 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm proud to announce the release of Wireshark 1.6.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.
o wnpa-sec-2012-08
Infinite and large loops in the ANSI MAP, ASF, BACapp,
Bluetooth HCI, IEEE 802.11, IEEE 802.3, LTP, and R3 dissectors
have been fixed. Discovered by Laurent Butti. (Bugs 6805,
7118, 7119, 7120, 7121, 7122, 7124, 7125)
Versions affected: 1.4.0 to 1.4.12, 1.6.0 to 1.6.7.
o wnpa-sec-2012-09
The DIAMETER dissector could try to allocate memory improperly
and crash. (Bug 7138)
Versions affected: 1.4.0 to 1.4.12, 1.6.0 to 1.6.7.
o wnpa-sec-2012-10
Wireshark could crash on SPARC processors due to misaligned
memory. Discovered by Klaus Heckelmann. (Bug 7221)
Versions affected: 1.4.0 to 1.4.12, 1.6.0 to 1.6.7.
The following bugs have been fixed:
o User-Password - PAP decoding passwords longer than 16 bytes.
(Bug 6779)
o The MSISDN is not seen correctly in GTP packet. (Bug 7042)
o Wireshark doesn't calculate the right IPv4 destination using
source routing options when bad options precede them. (Bug
7043)
o BOOTP dissector issue with DHCP option 82 - suboption 9. (Bug
7047)
o MPLS dissector in 1.6.7 and 1.7.1 misdecodes some MPLS CW
packets. (Bug 7089)
o ANSI MAP infinite loop. (Bug 7119)
o HCIEVT infinite loop. (Bug 7122)
o Wireshark doesn't decode NFSv4.1 operations. (Bug 7127)
o LTP infinite loop. (Bug 7124)
o Wrong values in DNS CERT RR. (Bug 7130)
o Megaco parser problem with LF in header. (Bug 7198)
o OPC UA bytestring node id decoding is wrong. (Bug 7226)
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
ANSI MAP, ASF, BACapp, Bluetooth HCI, DHCP, DIAMETER, DNS, GTP,
IEEE 802.11, IEEE 802.3, IPv4, LTP, Megaco, MPLS, NFS, OPC UA,
RADIUS
New and Updated Capture File Support
5View, CSIDS, pcap, pcap-ng
Getting Wireshark
Wireshark source code and installation packages are available from
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 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
Wireshark might make your system disassociate from a wireless
network on OS X 10.4. (Bug 1315)
Dumpcap might not quit if Wireshark or TShark crashes. (Bug 1419)
The BER dissector might infinitely loop. (Bug 1516)
Capture filters aren't applied when capturing from named pipes.
(Bug 1814)
Filtering tshark captures with display filters (-R) no longer
works. (Bug 2234)
The 64-bit Windows installer does not ship with libsmi. (Win64
development page)
"Closing File!" Dialog Hangs. (Bug 3046)
Application crash when changing real-time option. (Bug 4035)
Hex pane display issue after startup. (Bug 4056)
Packet list rows are oversized. (Bug 4357)
Summary pane selected frame highlighting not maintained. (Bug
4445)
Wireshark and TShark will display incorrect delta times when
displayed as a custom column. (Bug 4985)
Getting Help
Community support is available on 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 the
web site.
Training is available from Wireshark University.
Frequently Asked Questions
A complete FAQ is available on the Wireshark web site.
Digests
wireshark-1.6.8.tar.bz2: 21967111 bytes
MD5(wireshark-1.6.8.tar.bz2)=dcdc5f4904af5804b622c955a30974e2
SHA1(wireshark-1.6.8.tar.bz2)=fb79058c66944581b822e4d8370848f953cfc9d4
RIPEMD160(wireshark-1.6.8.tar.bz2)=858ee1bdcf61658356c1acd386135eb071205dd6
wireshark-win32-1.6.8.exe: 19599159 bytes
MD5(wireshark-win32-1.6.8.exe)=70668e1fe4dc233a962c1836ddbace88
SHA1(wireshark-win32-1.6.8.exe)=2a76df5b32c119039756196720b802f1e01f9b5b
RIPEMD160(wireshark-win32-1.6.8.exe)=61689ecc2460886828bfb01ae6aaa8beb4d44efd
wireshark-win64-1.6.8.exe: 22777173 bytes
MD5(wireshark-win64-1.6.8.exe)=4fef8d0dbcf0aeff321432d8d07adf04
SHA1(wireshark-win64-1.6.8.exe)=4134f492fdb4c965cc6cf50eddd5998a7dd0faf2
RIPEMD160(wireshark-win64-1.6.8.exe)=9f872c0a2a8157c0baf1e50352ca20cd3a60b396
wireshark-1.6.8.u3p: 26140280 bytes
MD5(wireshark-1.6.8.u3p)=d535487fb0aa184101ac85ef975e306c
SHA1(wireshark-1.6.8.u3p)=4e2094daec6558400f17ece69f3b514ad464a8f9
RIPEMD160(wireshark-1.6.8.u3p)=a5dd1dd7c525b3dea4a2be45bab5dcf29e4b00b0
WiresharkPortable-1.6.8.paf.exe: 20486553 bytes
MD5(WiresharkPortable-1.6.8.paf.exe)=b6deeaf385e22e28da1ea7da836e86b2
SHA1(WiresharkPortable-1.6.8.paf.exe)=ea1b46763294f1aadd4b38e9ea2de37f882f7742
RIPEMD160(WiresharkPortable-1.6.8.paf.exe)=8ac4816a3e3661b016d8a688950e3f2c785f1c1a
Wireshark 1.6.8 PPC 32.dmg: 21220745 bytes
MD5(Wireshark 1.6.8 PPC 32.dmg)=56c3e524201ed2063f2c99918c28562e
SHA1(Wireshark 1.6.8 PPC 32.dmg)=cd950165de242f24b259cb99fc673a74c40efa65
RIPEMD160(Wireshark 1.6.8 PPC
32.dmg)=edbd8fc48de5f0800084b06e257e065c8eb46a54
Wireshark 1.6.8 Intel 32.dmg: 20539108 bytes
MD5(Wireshark 1.6.8 Intel 32.dmg)=67359baa8ab9f3a7440e6e8fe4511833
SHA1(Wireshark 1.6.8 Intel
32.dmg)=5311017d5ff8ec8f752d8c2f6495541fd2d5dfb9
RIPEMD160(Wireshark 1.6.8 Intel
32.dmg)=1e19be2dcacd8fc7787be29960462e2b2a65ee05
Wireshark 1.6.8 Intel 64.dmg: 20326134 bytes
MD5(Wireshark 1.6.8 Intel 64.dmg)=1c0ff227075108bfa8ae018bb0168240
SHA1(Wireshark 1.6.8 Intel
64.dmg)=47cc629a5cac06a0ee571876fc8006f18ccd77d3
RIPEMD160(Wireshark 1.6.8 Intel
64.dmg)=ff6da09d2c50480e32bcf28ee9bca7bf202369b0
patch-wireshark-1.6.7-to-1.6.8.diff.bz2: 594418 bytes
MD5(patch-wireshark-1.6.7-to-1.6.8.diff.bz2)=1c449d514b791090162b4d74eb4e63c4
SHA1(patch-wireshark-1.6.7-to-1.6.8.diff.bz2)=814587ae54bcb3f0758ff5cf28a779af50d6a019
RIPEMD160(patch-wireshark-1.6.7-to-1.6.8.diff.bz2)=28f17de072168068daa5c7ef0b5359718f53d897
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+71zgACgkQpw8IXSHylJqJnwCfTf1wuOidnvixjCV1ypSyzBUq
6dYAni58zKBGSXHBH+wo4rFxkZp+OfqK
=I4xN
-----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-dev] Expected ABI breakage with 1.6.8
- Next by Date: [Wireshark-dev] Wireshark 1.4.13 is now available
- Previous by thread: Re: [Wireshark-dev] Possibly unsafe padding in Yahoo dissectors?
- Next by thread: [Wireshark-dev] Wireshark 1.4.13 is now available
- Index(es):