Wireshark 1.6.1 Release Notes

   ------------------------------------------------------------------

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.
