Wireshark-users: [Wireshark-users] Wireshark 1.2.5 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Thu, 17 Dec 2009 13:42:49 -0800
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.2.5. ------------------------------------------------------------------ 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 Daintree SNA file parser could overflow a buffer. (Bug 4294) Versions affected: 1.2.0 to 1.2.4 o The SMB and SMB2 dissectors could crash. (Bug 4301) Versions affected: 0.9.0 to 1.2.4 o The IPMI dissector could crash on Windows. (Bug 4319) Versions affected: 1.2.0 to 1.2.4 The following bugs have been fixed: o Wireshark does not graph rtp streams. (Bug 3801) o Wireshark showing extraneous data in a TCP stream. (Bug 3955) o Wrong decoding of gtp.target identification. (Bug 3974) o TTE dissector bug. (Bug 4247) o Upper case in Lua pref symbol causes Wireshark to crash. (Bug 4255) o OpenBSD 4.5 build fails at epan/dissectors/packet-rpcap.c. (Bug 4258) o Incorrect display of stream data using "Follow tcp stream" option. (Bug 4288) o Custom RADIUS dictionary can cause a crash. (Bug 4316) 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 DAP, eDonkey, GTP, IPMI, MIP, RADIUS, RANAP, SMB, SMB2, TCP, TTE, VNC, X.509sat Updated Capture File Support Daintree SNA. 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 may appear offscreen on multi-monitor Windows systems. (Bug 553) 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) Wireshark can't dynamically update the packet list. This means that host name resolutions above a certain response time threshold won't show up in the packet list. (Bug 1605) 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 the wireshark-users mailing list. Subscription information and archives for all of Wireshark's mailing lists can be found on the web site. Commercial support, training, and development services are available from CACE Technologies. Frequently Asked Questions A complete FAQ is available on the Wireshark web site. Digests wireshark-1.2.5.tar.bz2: 15296289 bytes MD5(wireshark-1.2.5.tar.bz2)=38010265a76f25553498304dcf15a92c SHA1(wireshark-1.2.5.tar.bz2)=46b74b82ae6bfad5f5f68ef1b3b7d453ae9b1087 RIPEMD160(wireshark-1.2.5.tar.bz2)=85f77a8a1c94999671c6e5226e4ced080176fbdd wireshark-1.2.5.tar.gz: 19349507 bytes MD5(wireshark-1.2.5.tar.gz)=fdc1bc9815ee7ba067094edf60f7b9ff SHA1(wireshark-1.2.5.tar.gz)=525b9062674a2951f790a2621ddf14e5cea5be48 RIPEMD160(wireshark-1.2.5.tar.gz)=ab0c2db7850eb4c8357756efe34eab9e1addba3f wireshark-win32-1.2.5.exe: 18337408 bytes MD5(wireshark-win32-1.2.5.exe)=83a93e4833adbcc54e6c9c0e6a989004 SHA1(wireshark-win32-1.2.5.exe)=e69035345e1ea94b9970ed5acc5b1815d2d9af32 RIPEMD160(wireshark-win32-1.2.5.exe)=88a8ded8375293939533ef944f824eb58c34142c wireshark-win64-1.2.5.exe: 19292166 bytes MD5(wireshark-win64-1.2.5.exe)=4c1531ce706000544618090acf3e3ce7 SHA1(wireshark-win64-1.2.5.exe)=be3d931850840932721c90a6b9d27ed3018d1ab7 RIPEMD160(wireshark-win64-1.2.5.exe)=0766f8bd5048570badfd3356f9cb7bb301e2483f wireshark-1.2.5.u3p: 21472637 bytes MD5(wireshark-1.2.5.u3p)=55ebfa267f67b1d29177fb2095e68210 SHA1(wireshark-1.2.5.u3p)=1d5ca8b26fc1457200a527ad618d00de72571040 RIPEMD160(wireshark-1.2.5.u3p)=6f6691f0e56348bdf96b327f7f36d3328bf04509 WiresharkPortable-1.2.5.paf.exe: 19155791 bytes MD5(WiresharkPortable-1.2.5.paf.exe)=4d3d8d852bd42172a26c19da0ce788d2 SHA1(WiresharkPortable-1.2.5.paf.exe)=d01d324a556cb62bab01e48dea85c84d63d2366a RIPEMD160(WiresharkPortable-1.2.5.paf.exe)=1482c8aaf7b268c53ff6169693802ad332db011f Wireshark 1.2.5 Intel.dmg: 42399798 bytes MD5(Wireshark 1.2.5 Intel.dmg)=aa229ece64a6a7e7c98df6d3bda40266 SHA1(Wireshark 1.2.5 Intel.dmg)=d11d48f161a366b5823cc2f65ee16452188bf530 RIPEMD160(Wireshark 1.2.5 Intel.dmg)=333d247850f267f8088956036af4d159f1af7b69 Wireshark 1.2.5 PPC.dmg: 44539023 bytes MD5(Wireshark 1.2.5 PPC.dmg)=38d965db02e276a94a6d70875f7338b1 SHA1(Wireshark 1.2.5 PPC.dmg)=a7476c11bfc1df83c05d58accebc6cdc55df504a RIPEMD160(Wireshark 1.2.5 PPC.dmg)=6d804b5a1eb77fe7b9bf0ce7840fc05477d17313 patch-wireshark-1.2.4-to-1.2.5.diff.bz2: 142672 bytes MD5(patch-wireshark-1.2.4-to-1.2.5.diff.bz2)=fd52261e0a9c9d250bc1f1643a3577b8 SHA1(patch-wireshark-1.2.4-to-1.2.5.diff.bz2)=8111d815935e54a0f6bd61daa3779807193edc7e RIPEMD160(patch-wireshark-1.2.4-to-1.2.5.diff.bz2)=72139f1e254a5e2c51417911d34d9b15c090cc7f -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksqpdkACgkQpw8IXSHylJqn0QCgs3zI8GAdJzfLGyTvBfWuZp4e YRsAn1phX350LSbC4P0nogxaVK3mwW8a =T0yN -----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-users] WIRESHARK Version 8.1.0 problems in DSCP coding
- Next by Date: [Wireshark-users] tshark reassembled TLSv1 record: Can it display certificate attributes for each certificate in a chain?
- Previous by thread: Re: [Wireshark-users] WIRESHARK Version 8.1.0 problems in DSCP coding
- Next by thread: [Wireshark-users] tshark reassembled TLSv1 record: Can it display certificate attributes for each certificate in a chain?
- Index(es):