Wireshark-users: [Wireshark-users] Wireshark 1.2.3 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 27 Oct 2009 14:28:32 -0700
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.2.3. 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 Paltalk dissector could crash on alignment-sensitive processors. (Bug 3689) Versions affected: 1.2.0 to 1.2.2 o The DCERPC/NT dissector could crash. Versions affected: 0.10.10 to 1.2.2 o The SMB dissector could crash. Versions affected: 1.2.0 to 1.2.2 The following bugs have been fixed: o Wireshark memory leak with each file open and/or display filter change. (Bug 2375) o DHCP Dissector displays negative lease time. (Bug 2733) o Invalid advertised window line on tcptrace style graph. (Bug 3417) o SMB get_dfs_referral referral entry is not dissected correctly. (Bug 3542) o Error dissecting eMule sourceOBFU message. (Bug 3848) o Typos in Diameter XML files. (Bug 3878) o RSL dissector for MS Power IE is broken. (Bug 4017) o Manifest problem in 1.2.2 Win64 build. (Bug 4024) o FIP dissector throws assertion. (Bug 4046) o TCAP problem with indefinite length 'components' SEQ OF. (Bug 4053) o GSM MAP: an-APDU not decoded. (Bug 4095) o Add "Drag and Drop entries..." message on Columns preferences page. (Bug 4099) o Editcap -t and -w option parses fractional digits incorrectly. (Bug 4162) New and Updated Features The 32-bit and 64-bit Windows packages now include WinPcap 4.1.1. New Protocol Support There are no new protocols in this release. Updated Protocol Support DCERPC NT, DHCP, Diameter, E.212, eDonkey, FIP, IPsec, MGCP, NCP, Paltalk, RADIUS, RSL, SBus, SMB, SNMP, SSL, TCP, Teamspeak2, WPS Updated Capture File Support Capture file support is unchanged in this release. Getting Wireshark Wireshark source code and installation packages are available from the download page on the main web site. 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. 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.3.tar.bz2: 15215978 bytes MD5(wireshark-1.2.3.tar.bz2)=c2dfc197e485a0b0072ca64b8ac4d24c SHA1(wireshark-1.2.3.tar.bz2)=be69e1ea13cf63742fd71c69c02e658eec109d18 RIPEMD160(wireshark-1.2.3.tar.bz2)=477565e97a05abba82faf5cd817de5281434fc78 wireshark-1.2.3.tar.gz: 19293381 bytes MD5(wireshark-1.2.3.tar.gz)=607eb3416e6240e4236ea5eb6eb6b6f1 SHA1(wireshark-1.2.3.tar.gz)=cac65da21cd203bf5a4b51f56296ffe30c4b30a3 RIPEMD160(wireshark-1.2.3.tar.gz)=c5c195e022b1ec6b950e12b99b93bd91d3916f0f wireshark-win32-1.2.3.exe: 18303147 bytes MD5(wireshark-win32-1.2.3.exe)=dda57dd93ec45bae3c8df36de4a94fe9 SHA1(wireshark-win32-1.2.3.exe)=368c0b8cbf5caf699647ad6ba431ee416d9c28fd RIPEMD160(wireshark-win32-1.2.3.exe)=42a1e7f851842ef8fb186ac71e44c7ba2db74916 wireshark-win64-1.2.3.exe: 19179311 bytes MD5(wireshark-win64-1.2.3.exe)=c26323bcb19d8416c3c56a3807391646 SHA1(wireshark-win64-1.2.3.exe)=5700d973cc7bf6162db8db6d670ddd01f424f8d8 RIPEMD160(wireshark-win64-1.2.3.exe)=e8e5e74c1beb1dde3eb9824961c5886a77f394bd wireshark-1.2.3.u3p: 21501263 bytes MD5(wireshark-1.2.3.u3p)=c92beae07d509b3305134169591bee3c SHA1(wireshark-1.2.3.u3p)=34acd8f08ffba25b4fbbb2a85335b98b1a20a9df RIPEMD160(wireshark-1.2.3.u3p)=3e143edbeeab5f880c798e9db06a9aa50142fcfc WiresharkPortable-1.2.3.paf.exe: 19201903 bytes MD5(WiresharkPortable-1.2.3.paf.exe)=314b24c69a123213073ca1a029f69b5e SHA1(WiresharkPortable-1.2.3.paf.exe)=83f86295b7c655de5dbc7ed3767392ee5f7c94c2 RIPEMD160(WiresharkPortable-1.2.3.paf.exe)=7b5755b96170aaeff99c661ae567355d06951d97 Wireshark 1.2.3 Intel.dmg: 42366073 bytes MD5(Wireshark 1.2.3 Intel.dmg)=1d0f7dd5ecbd0d764a1f72be1341f6cc SHA1(Wireshark 1.2.3 Intel.dmg)=e9b6c9621cc74e5e2e0639905c71e0972622f10d RIPEMD160(Wireshark 1.2.3 Intel.dmg)=cdd16c95e6b66e25bbc2a5e6937629dafd3a3857 Wireshark 1.2.3 PPC.dmg: 44510452 bytes MD5(Wireshark 1.2.3 PPC.dmg)=a0cb726784f4521d87bc2a3badd9d9be SHA1(Wireshark 1.2.3 PPC.dmg)=b5209a7e2f7aed82c3e08a8b2061f165741207a6 RIPEMD160(Wireshark 1.2.3 PPC.dmg)=0b6adeec244c6e198fe82d43fa1190f2aba99852 patch-wireshark-1.2.2-to-wireshark-1.2.3.diff.bz2: 79699 bytes MD5(patch-wireshark-1.2.2-to-wireshark-1.2.3.diff.bz2)=0b11604fbb06edd1e707d31dd97bec9e SHA1(patch-wireshark-1.2.2-to-wireshark-1.2.3.diff.bz2)=55c9d7c7f823a54e2da7f7fa280aab5ff3f234f7 RIPEMD160(patch-wireshark-1.2.2-to-wireshark-1.2.3.diff.bz2)=9778cd3915a1ce287f9d1855da52aa8a61fd1302 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrnZgAACgkQpw8IXSHylJqOBgCgjJPWxxK4v5uaiCBH5kKA45IL 8FoAoJL4iLk+qaRGuOuDctTA/IWa1zGx =sqPz -----END PGP SIGNATURE-----
- Prev by Date: [Wireshark-users] Wireshark 1.0.10 is now available
- Next by Date: Re: [Wireshark-users] Wireshark Network protocol analyzer version 1.0.3
- Previous by thread: [Wireshark-users] Wireshark 1.0.10 is now available
- Next by thread: [Wireshark-users] Disabling TCP Checksum
- Index(es):