Wireshark-users: [Wireshark-users] Wireshark 1.6.1 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Mon, 18 Jul 2011 16:18:24 -0700
I'm proud to announce the release of Wireshark 1.6.1.
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. See the security
advisory for details and a workaround.
o The Lucent/Ascend file parser was susceptible to an infinite
loop.
Versions affected: 1.2.0 to 1.2.17, 1.4.0 to 1.4.7, and 1.6.0.
CVE-2011-2597
o The ANSI MAP dissector was susceptible to an infinite loop.
(Bug 6044)
Versions affected: 1.4.0 to 1.4.7, and 1.6.0.
The following bugs have been fixed:
o TCP dissector doesn't decode TCP segments of length 1. (Bug
4716)
o wireshark 1.4.0rc1 and python - spurious message. (Bug 4878)
o Missing LUA function. (Bug 5006)
o Lua API description about creating a new Tvb from a bytearray
is not correct in wireshark's user guide. (Bug 5199)
o Character echo pauses in Capture Filter field in Capture
Options. (Bug 5356)
o White space in protocol field abbreviation causes runtime
failure while registering Lua dissector. (Bug 5569)
o "File not found" box uses wrong filename encoding. (Bug 5715)
o capinfos: #ifdef HAVE_LIBGCRYPT block includes a line too many
. (Bug 5803)
o Wireshark crashes if Lua contains "Pref.range()" with missing
arguments. (Bug 5895)
o The "range" field in Lua's "Pref.range()" serves as default
while the "default" field does nothing . (Bug 5896)
o Wireshark crashes when calling TreeItem:set_len() on TreeItem
without tvb. (Bug 5941)
o TvbRange_string(lua_State* L) call a wrong function. (Bug
5960)
o VoIP call flow graph displays BICC APM as a BICC ANM. (Bug
5966)
o Cannot Live-capture VirtualBox network packets with Wireshark;
pipe problem. (Bug 6002)
o Interface list in Capture Options isn't cleared when selecting
other host. (Bug 6008)
o H323 rate multiplier wrong. (Bug 6009)
o Inclusion of config.h is too late in lex-files resulting in
wrong definition of _FILE_OFFSET_BITS. (Bug 6012)
o tshark crashes when loading Lua script that contains GUI
function. (Bug 6018)
o 802.11 Disassociation Packet's "Reason Code" field is
imprecisely decoded/described. (Bug 6022)
o Wireshark crashes when setting custom column's field name with
conditional. (Bug 6028)
o Crash after applying "expert.severity" field as column. (Bug
6035)
o GTS Descriptor count limited to 3 instead of 7. (Bug 6055)
o The SSL dissector can not resemble correctly the frames after
TCP zero window probe packet. (Bug 6059)
o Packet parser takes too long for this trace. (Bug 6073)
o The SSL dissector can not resemble correctly the frames after
TCP zero window probe packet. (Bug 6059)
o Wireshark crashes after repeating "File -> Import -> Cancel".
(Bug 6080)
o Decoding of MQ ASCII and EBCDIC Traffic Flow - ASCII shows
fine, EBCDIC does not. (Bug 6084)
o 802.11 Association Response Packet's "Status Code" field is
imprecisely decoded/described. (Bug 6093)
o Abis interface not correctly handled in gsmtap dissector. (Bug
6097)
o Wrong decoding of RLC/MAC EGPRS Packet Downlink Ack/Nack (3GPP
TS 44.060). (Bug 6098)
o CSN Ack/Nack Description wrongly handled in gsm_rlcmac_dl
dissector (3GPP TS 44.060). (Bug 6101)
o wireshark 1.6.0 and python support: installer fails to create
the wspy_dissectors subdirectory and . (Bug 6110)
o Wireshark crash during RTP stream analysis. (Bug 6120)
o Tshark custom columns: Why don't I get an error message? (Bug
6131)
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
New and Updated Capture File Support
Network Monitor.
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)
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 in some
cases. (Bug 4985 and bug 5580)
Character echo pauses in Capture Filter field in Capture Options.
(Bug 5356)
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.1.tar.bz2: 21305013 bytes
MD5(wireshark-1.6.1.tar.bz2)=dc1e8c9800b64130674b120a183e2308
SHA1(wireshark-1.6.1.tar.bz2)=e4ff6150f25be96a0b1d7e33da51001d453e7828
RIPEMD160(wireshark-1.6.1.tar.bz2)=ef1f76f2b1abe7db253f80e36546aa2d828268b3
wireshark-win32-1.6.1.exe: 19472996 bytes
MD5(wireshark-win32-1.6.1.exe)=730ff98b0061a73cdf74f946a0a99c88
SHA1(wireshark-win32-1.6.1.exe)=fe8820f2c13bec9e3df118a5c2e95e7fe2be740a
RIPEMD160(wireshark-win32-1.6.1.exe)=fb53aba13b8f5fde5f94a603ad2f492d8b0185ed
wireshark-win64-1.6.1.exe: 22651897 bytes
MD5(wireshark-win64-1.6.1.exe)=3434f294e8ac88668637ff2096d0c544
SHA1(wireshark-win64-1.6.1.exe)=e9b452cdde8dde1268b0170477b2d27a3b4b3405
RIPEMD160(wireshark-win64-1.6.1.exe)=63d55cb9481b3052e33d423bd3a01fc8104cf18d
wireshark-1.6.1.u3p: 25900688 bytes
MD5(wireshark-1.6.1.u3p)=152036618bf287bd7513ebeceac6a507
SHA1(wireshark-1.6.1.u3p)=c15cd071b7fcb88f23357297cb6e0e224d01e197
RIPEMD160(wireshark-1.6.1.u3p)=a163b6c7b67c0a57dc3c433ab41a6bfe0c5a5589
WiresharkPortable-1.6.1.paf.exe: 20369721 bytes
MD5(WiresharkPortable-1.6.1.paf.exe)=ac863edcde3af2548bcf9b496ecd3166
SHA1(WiresharkPortable-1.6.1.paf.exe)=37b333bd50c90fa49e046bd53fcdc4e13e95ea20
RIPEMD160(WiresharkPortable-1.6.1.paf.exe)=2526b6f676dbe7e0a34082dd4519dad225c4d15f
Wireshark 1.6.1 Intel 32.dmg: 20294100 bytes
MD5(Wireshark 1.6.1 Intel 32.dmg)=dc71c119bf4a78884fc9578c50de036f
SHA1(Wireshark 1.6.1 Intel 32.dmg)=bf6ad18d310efb45b1aaf6f8a470d9f4636166e5
RIPEMD160(Wireshark 1.6.1 Intel
32.dmg)=231d97fa557d6285fc1ebaeec7cd79e30f4d2828
Wireshark 1.6.1 Intel 64.dmg: 19831672 bytes
MD5(Wireshark 1.6.1 Intel 64.dmg)=598fd91ffdddd948309b9c66999bec52
SHA1(Wireshark 1.6.1 Intel 64.dmg)=9b3314d96f95936c0a6a51af670971b3891553a5
RIPEMD160(Wireshark 1.6.1 Intel
64.dmg)=5192787a02641e4542813112eeba523c77151f70
Wireshark 1.6.1 PPC 32.dmg: 21009395 bytes
MD5(Wireshark 1.6.1 PPC 32.dmg)=40d0982fc87da2f846002fcddb5b9961
SHA1(Wireshark 1.6.1 PPC 32.dmg)=904912edd0775b7f9b8d06c09612bde97310f132
RIPEMD160(Wireshark 1.6.1 PPC
32.dmg)=d3287297b29b21f2171d1ba82635296bde62d47a
patch-wireshark-1.6.0-to-1.6.1.diff.bz2: 777912 bytes
MD5(patch-wireshark-1.6.0-to-1.6.1.diff.bz2)=ee15d963d1fa0d3ead2c1810e7f4e3b0
SHA1(patch-wireshark-1.6.0-to-1.6.1.diff.bz2)=45d9056e83fef2178407b715beebc48f25fda6c6
RIPEMD160(patch-wireshark-1.6.0-to-1.6.1.diff.bz2)=89ae73df71f72c32e8494b8f9671d69155fd23ef
- Prev by Date: Re: [Wireshark-users] finding the smoking gun for traffic spikes
- Next by Date: [Wireshark-users] Wireshark 1.4.8 is now available
- Previous by thread: Re: [Wireshark-users] CVE-2011-2597
- Next by thread: [Wireshark-users] Wireshark 1.4.8 is now available
- Index(es):