Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: [Wireshark-users] Wireshark 1.4.8 is now available

From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Mon, 18 Jul 2011 16:18:39 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm proud to announce the release of Wireshark 1.4.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. 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 sflow decode error for some extended formats. (Bug 5379)

     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 H323 rate multiplier wrong. (Bug 6009)

     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 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 802.11 Association Response Packet's "Status Code" field is
       imprecisely decoded/described. (Bug 6093)

     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

   ANSI MAP, GIOP, H.323, IEEE 802.11, MSRP, RPCAP, sFlow, TCP,

  New and Updated Capture File Support

   Lucent/Ascend.

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 the same libraries
   as the 32-bit installer. (Bug 3610)

   Hex pane display issue after startup. (Bug 4056)

   Packet list rows are oversized. (Bug 4357)

   Summary pane selected frame highlighting not maintained. (Bug
   4445)

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.4.8.tar.bz2: 20505798 bytes
MD5(wireshark-1.4.8.tar.bz2)=d0cf6c24b00071efb356328c8d9c03a7
SHA1(wireshark-1.4.8.tar.bz2)=8f9d0a920d00ac22ae0b2fa5844adbadc7e2de1e
RIPEMD160(wireshark-1.4.8.tar.bz2)=970ada8ccbbca17695038faf4c0bca83d126d9a4

wireshark-win32-1.4.8.exe: 19497636 bytes
MD5(wireshark-win32-1.4.8.exe)=a92d3c426c0681ad0416d250c183bd0b
SHA1(wireshark-win32-1.4.8.exe)=e9590b62681a7acd18b792d1c3a4bdc38e9b1f32
RIPEMD160(wireshark-win32-1.4.8.exe)=4a0d54f3edf8f7437dcfd2664e6a939f721b62f9

wireshark-win64-1.4.8.exe: 21771666 bytes
MD5(wireshark-win64-1.4.8.exe)=78b83103c40412b1b308dd810a173352
SHA1(wireshark-win64-1.4.8.exe)=59c834ba4bcb43534b1f2ab41313becfd6d8bb76
RIPEMD160(wireshark-win64-1.4.8.exe)=738c4c61cf01bac2ab4e3ec108619b74e4d9e296

wireshark-1.4.8.u3p: 25857837 bytes
MD5(wireshark-1.4.8.u3p)=a2f97869b2dab6cdff8101cfdb30b140
SHA1(wireshark-1.4.8.u3p)=dad1baefaeae5c8eab575f856930e9ec8d5469f8
RIPEMD160(wireshark-1.4.8.u3p)=e240f2ed74b7efc9d2b1bd1e5af5bb787aa338e4

WiresharkPortable-1.4.8.paf.exe: 20434700 bytes
MD5(WiresharkPortable-1.4.8.paf.exe)=87f6b6e6f991bf49f9a2453c4a0386e5
SHA1(WiresharkPortable-1.4.8.paf.exe)=d761b17a916c93cf236c06664c9f93cf9d82145c
RIPEMD160(WiresharkPortable-1.4.8.paf.exe)=aa41c954acd820a6c72dc6abf8f04a1b0b74880d

Wireshark 1.4.8 Intel 32.dmg: 47664202 bytes
MD5(Wireshark 1.4.8 Intel 32.dmg)=39ecda677e2f044397677250f9ed977a
SHA1(Wireshark 1.4.8 Intel 32.dmg)=cf37c354687a473678112e47668e1044fea2e04b
RIPEMD160(Wireshark 1.4.8 Intel
32.dmg)=367b8cece03cd8403469c68404823030ad703d7f

Wireshark 1.4.8 Intel 64.dmg: 45062679 bytes
MD5(Wireshark 1.4.8 Intel 64.dmg)=d5c1e76aebe07ff2280bbd48377fb63d
SHA1(Wireshark 1.4.8 Intel 64.dmg)=75426d0f9db50a3dadaa60d01f75f13791ee21e2
RIPEMD160(Wireshark 1.4.8 Intel
64.dmg)=ee20313cffbd1f56f1ecdfbc5dcc66332f1f6aaa

Wireshark 1.4.8 PPC 32.dmg: 50181423 bytes
MD5(Wireshark 1.4.8 PPC 32.dmg)=8f9a77c4fb7c851aac59c1e12cb98432
SHA1(Wireshark 1.4.8 PPC 32.dmg)=8d6d043367116dce1175c01263f7e1bcc14fdd8f
RIPEMD160(Wireshark 1.4.8 PPC
32.dmg)=9a9a7abdd5f0cd944af0364123b408c47e8f5be1

patch-wireshark-1.4.7-to-1.4.8.diff.bz2: 15821758 bytes
MD5(patch-wireshark-1.4.7-to-1.4.8.diff.bz2)=004178219c4ec192098ea936772dc043
SHA1(patch-wireshark-1.4.7-to-1.4.8.diff.bz2)=9de73741e9e26d654ff52afff6918787851b63cd
RIPEMD160(patch-wireshark-1.4.7-to-1.4.8.diff.bz2)=83bb034127f7787a7fd3e944ae8f76d280383c25
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4kv08ACgkQpw8IXSHylJrtVQCgnWmUoOerJK++scsGJ7QC7kqE
umUAoNgQwRFktQiPMPbN1VvKxXU61dSP
=XjTd
-----END PGP SIGNATURE-----