Wireshark-users: [Wireshark-users] Wireshark 1.2.18 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 28 Jun 2011 13:14:59 -0700
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.2.18. NOTE: The 1.2.x series of Wireshark releases will reach end of life on June 30, 2011. If you are still using Wireshark 1.2 we strongly encourage you to upgrade to 1.6. 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. The following bugs have been fixed: o Missing LUA function. (Bug 5006) o Lua API description about creating a new Tvb from a bytearray is not correct in User's Guide. (Bug 5199) o White space in protocol field abbreviation causes runtime failure while registering Lua dissector. (Bug 5569) o Wireshark will not run on Windows 2000. (Bug 5874) 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 Wireshark crashes if Lua contains "Pref.range()" with missing arguments. (Bug 5985) o The "range" field in Lua's "Pref.range()" serves as default while the "default" field does nothing. (Bug 5896) o TShark crashes when loading Lua script that contains GUI function. (Bug 6018) 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 Updated Capture File Support There are no capture file support updates in this release. 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. (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) Wireshark might freeze when reading from a pipe. (Bug 2082) 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) 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.2.18.tar.bz2: 15455303 bytes MD5(wireshark-1.2.18.tar.bz2)=ffb4eb79a9c24148bdc700bfe7cda66f SHA1(wireshark-1.2.18.tar.bz2)=4194eec4af9afbaa08fcd5e6d946f06313b3b187 RIPEMD160(wireshark-1.2.18.tar.bz2)=88a6119778b0ce06a070f75b427347af90e3e505 wireshark-1.2.18.tar.gz: 19613406 bytes MD5(wireshark-1.2.18.tar.gz)=07781c2981e3524f9e09b4470bdede6a SHA1(wireshark-1.2.18.tar.gz)=2947049c1344cdcd846b142700d8f9b18985bec2 RIPEMD160(wireshark-1.2.18.tar.gz)=8ff0dd33880bb5f92e8a201de805eae2f8121cae wireshark-win32-1.2.18.exe: 18172147 bytes MD5(wireshark-win32-1.2.18.exe)=b2873dc0a8ad3ef006cec9d1cbfddea6 SHA1(wireshark-win32-1.2.18.exe)=a05fc872bd74f25e2d1348083247ee656c396c05 RIPEMD160(wireshark-win32-1.2.18.exe)=4bf54523b15bd9e6ae1710c56eb45aab3a85f73f wireshark-win64-1.2.18.exe: 20462652 bytes MD5(wireshark-win64-1.2.18.exe)=a7afba6ea74cec21cb9f3309ec4d4d75 SHA1(wireshark-win64-1.2.18.exe)=3f86e16dff618a2fb508e1178aeca2a6ce43b9cd RIPEMD160(wireshark-win64-1.2.18.exe)=fb1866eedd1eb87bddcf59bab874e6047834f41c wireshark-1.2.18.u3p: 21263823 bytes MD5(wireshark-1.2.18.u3p)=8303edf0c65e702756a9558db6090885 SHA1(wireshark-1.2.18.u3p)=9923fea3d4ace9a25863055531aadceb0ef809a2 RIPEMD160(wireshark-1.2.18.u3p)=70ab9332c388a4a1edbb6bec0d73638db3b226f0 WiresharkPortable-1.2.18.paf.exe: 18816217 bytes MD5(WiresharkPortable-1.2.18.paf.exe)=2e3354c514ed9fb95d4bc6f9d19a8fd4 SHA1(WiresharkPortable-1.2.18.paf.exe)=b088121d2cd9b68e1b912be102f21509c9036474 RIPEMD160(WiresharkPortable-1.2.18.paf.exe)=311a9675b37bd36e9bf4d2af381bb85a24bdf1b6 Wireshark 1.2.18 Intel.dmg: 42669020 bytes MD5(Wireshark 1.2.18 Intel.dmg)=da11a2b6c00b0e38af3b484de115434c SHA1(Wireshark 1.2.18 Intel.dmg)=562b80c4ca4db0d9040e1f53f6557499c242ec11 RIPEMD160(Wireshark 1.2.18 Intel.dmg)=971faf958fa3d0cf3c3e095e7b5108ac3e4d249d Wireshark 1.2.18 PPC.dmg: 44829190 bytes MD5(Wireshark 1.2.18 PPC.dmg)=89c9c5f07c7cc378dbc2e21ae33b61ef SHA1(Wireshark 1.2.18 PPC.dmg)=0b787137421b4ec49f66f03d1d4dd85f5685dca2 RIPEMD160(Wireshark 1.2.18 PPC.dmg)=df128504bfee51c38d8d859567351276b9e67c61 patch-wireshark-1.2.17-to-1.2.18.diff.bz2: 46539 bytes MD5(patch-wireshark-1.2.17-to-1.2.18.diff.bz2)=87b3eafb78e87d7eefb3590629085f63 SHA1(patch-wireshark-1.2.17-to-1.2.18.diff.bz2)=4581ea53e818ab2c1df06e3a5e1973176f24ffda RIPEMD160(patch-wireshark-1.2.17-to-1.2.18.diff.bz2)=854ccc49026d087e60799c1e942167887e76aa20 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4KNkMACgkQpw8IXSHylJrGjgCgzi4geUZIf+Q4D0NXR/dOjvdq wsEAoKFz1IWLL8zkozfrtm9leMyhQEhW =Q6wf -----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-users] text2pcap - strange packets after converting a Hex-dump
- Next by Date: Re: [Wireshark-users] Something like editcap?
- Previous by thread: Re: [Wireshark-users] Difference between TCP Window size and data length
- Index(es):