Wireshark-users: [Wireshark-users] Wireshark 1.0.5 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 10 Dec 2008 10:16:32 -0800
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.0.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 SMTP dissector could consume excessive amounts of CPU and memory. Versions affected: 1.0.4 o The WLCCP dissector could go into an infinte loop. Versions affected: 0.99.7 to 1.0.4 The following bugs have been fixed: o Missing CRLF during HTTP POST in the "packet details" window (Bug 2534) o Memory assertion in time_secs_to_str_buf() when compiled with GCC 4.2.3 (Bug 2777) o Diameter dissector fails RFC 4005 compliance (Bug 2828) o LDP vendor private TLV type is not correctly shown (Bug 2832) o Wireshark on MacOS does not run when there are spaces in its path (Bug 2844) o OS X Intel package incorrectly claims to be Universal (Bug 2979) o Compilation broke when compiling without zlib (Bug 2993) o Memory leak: saved_repoid (Bug 3017) o Memory leak: follow_info (Bug 3018) o Memory leak: follow_info (Bug 3019) o Memory leak: tacplus_data (Bug 3020) o Memory leak: col_arrows (Bug 3021) o Memory leak: col_arrows (Bug 3022) o Incorrect address structure assigned for find_conversation() in WSP (Bug 3071) o Memory leak with unistim in voip_calls (Bug 3079) o Error parsing the BSSGP protocol (Bug 3085) o Assertion thrown in fvalue_get_uinteger when decoding TIPC (Bug 3086) o LUA script : Wireshark crashes after closing and opening again a window used by a listener.draw() function. (Bug 3090) New and Updated Features There are no new or updated features in this release. New Protocol Support There are no new protocols in this release. Updated Protocol Support ANSI MAP, BSSGP, CIP, Diameter, ENIP, GIOP, H.263, H.264, HTTP, MPEG PES, PostgreSQL, PPI, PTP, Rsync, RTP, SMTP, SNMP, STANAG 5066, TACACS, TIPC, WLCCP, WSP New and Updated Capture File Support None 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) Capturing from named pipes might be delayed on Windows. (Bug 2200) Filtering tshark captures with display filters (-R) no longer works. (Bug 2234) 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 and development services are available from CACE Technologies. Frequently Asked Questions A complete FAQ is available on the Wireshark web site. Digests wireshark-1.0.5.tar.bz2: 13144320 bytes MD5(wireshark-1.0.5.tar.bz2)=4c6a93e00123d8bb7af48a009519aca4 SHA1(wireshark-1.0.5.tar.bz2)=593aaf3a7527e8ca74e4982caeb5a77831b121db RIPEMD160(wireshark-1.0.5.tar.bz2)=72b1ac2e78a02e84525b6ecd6563698b5b7474fc wireshark-1.0.5.tar.gz: 16861293 bytes MD5(wireshark-1.0.5.tar.gz)=99ac9a9d2c1445658039f1f34c89e3f6 SHA1(wireshark-1.0.5.tar.gz)=1651026e377aab2a4b7f07a9539f5754f034790c RIPEMD160(wireshark-1.0.5.tar.gz)=4a8dc703ec1e1387e297dbd4d668faf2afd27baf wireshark-setup-1.0.5.exe: 22245185 bytes MD5(wireshark-setup-1.0.5.exe)=c79f0b8ce5f61f9db295cb205eae53f9 SHA1(wireshark-setup-1.0.5.exe)=7a9687828d32119465e98dcd14e1bf4149a30b6f RIPEMD160(wireshark-setup-1.0.5.exe)=323942ea21a70750e8c0104409197d2d32f2cbb8 wireshark-1.0.5.u3p: 20116233 bytes MD5(wireshark-1.0.5.u3p)=75a5ee96296485c15cd83a751d8e64b4 SHA1(wireshark-1.0.5.u3p)=a1a7a69a76b86018c56ad39056249138a5c1ea48 RIPEMD160(wireshark-1.0.5.u3p)=d674158c2bf57d8cb39e9179bf379a847c5e8527 WiresharkPortable-1.0.5.paf.exe: 17547297 bytes MD5(WiresharkPortable-1.0.5.paf.exe)=ea8f310b97d5080d7e05df12547f669d SHA1(WiresharkPortable-1.0.5.paf.exe)=8e845156c0e6115edf3c534b69542fa61df57bd9 RIPEMD160(WiresharkPortable-1.0.5.paf.exe)=e79e5a470e27cae103467d7e743dde38b6ae65a2 Wireshark 1.0.5 Intel.dmg: 31282540 bytes MD5(Wireshark 1.0.5 Intel.dmg)=032f2d59d16c3933c105d5951b5d2c3d SHA1(Wireshark 1.0.5 Intel.dmg)=db415b48ed41b6f7ded3a8ac8d4300c5a3277141 RIPEMD160(Wireshark 1.0.5 Intel.dmg)=f8992dc816f16b0bff5697e7b23b0c7569e833cf Wireshark 1.0.5 PPC.dmg: 34647867 bytes MD5(Wireshark 1.0.5 PPC.dmg)=aa2719d904ff4394ae88f1453e1e6178 SHA1(Wireshark 1.0.5 PPC.dmg)=562b62f93aef207df6700a1b35bcbf9fc0688bfe RIPEMD160(Wireshark 1.0.5 PPC.dmg)=c1ded8fac3736fe51a8ae1a71a2b624c826a5d49 patch-wireshark-1.0.4-to-1.0.5.diff.bz2: 149948 bytes MD5(patch-wireshark-1.0.4-to-1.0.5.diff.bz2)=7289383b0dcd6ff151b621a33cbc6936 SHA1(patch-wireshark-1.0.4-to-1.0.5.diff.bz2)=8128f4a88d9b1e3206a1a816af4ab4b0265a4ec1 RIPEMD160(patch-wireshark-1.0.4-to-1.0.5.diff.bz2)=d9bc0c62e6b8f7890db6b644d0ce3a38891f3eeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAklAB30ACgkQpw8IXSHylJoB6gCfWmXs/R6B2Sh+ZNgWFn9kqj61 Zw0An2o3HsCj/dfungCSHN6MD8Da8qw/ =5Dd8 -----END PGP SIGNATURE-----
- Prev by Date: [Wireshark-users] Wireshark Bug 3046
- Next by Date: [Wireshark-users] RIP vs Ping
- Previous by thread: [Wireshark-users] Wireshark Bug 3046
- Next by thread: [Wireshark-users] RIP vs Ping
- Index(es):