Wireshark-users: [Wireshark-users] Wireshark 1.0.3 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 03 Sep 2008 21:52:41 -0700
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.0.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 NCP dissector was susceptible to a number of problems, including buffer overflows and an infinite loop. Versions affected: 0.9.7 to 1.0.2 o Wireshark could crash while uncompressing zlib-compressed packet data. Versions affected: 0.10.14 to 1.0.2 o Wireshark could crash while reading a Tektronix .rf5 file. Versions affected: 0.99.6 to 1.0.2 The following bugs have been fixed: o 802.11 WPA/WPA2-PSK Unable to decode Group Keys. (Bug 1420) o Packets could wrongly be dissected as "Redback Lawful Intercept" (Bug 2376) o MIKEY dissector improvements (Bug 2400) o tvb_get_bits{16|32} could read past the end of a tvbuff (Bug 2439) o Incorrect wslua function names. (Bug 2448) o Memory corruption in wslua. (Bug 2453) o Unknown PPPoE TAGs which are present in a PPPoE discovery packet are not displayed under "PPPoE Tags" subtree/section. (Bug 2458) o Following a TCP stream could incorrectly reassemble packets. (Bug 2606) o SIP decode shows fully expanded "Content-Length" header instead of compact form. (Bug 2635) o Segmentation fault loading trace containing NCP packets. (Bug 2675) o SIP packets might incorrectly be displayed as malformed. (Bug 2729) o RTCP BYE padding interpreted incorrectly. (Bug 2778) o Reversed RTP stream is saved as silent .au file, forward stream saves correctly. (Bug 2780) o Fix some lint warnings. (Bug 2822) o Setting a duration on a capture file would capture for an extra second. 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 AIM, Bluetooth RFCOMM, ERF, K12, NCP, PPP BCP, PPPoE, Q.933, Redback LI, RTCP, RTP, SIP, SNMP, TCP, V.120, WiMAX New and Updated Capture File Support Endace ERF, Tektronix .rf5. 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.3.tar.bz2: 13104737 bytes MD5(wireshark-1.0.3.tar.bz2)=1f9bacf6df9150a8dd8fe862a4be27a8 SHA1(wireshark-1.0.3.tar.bz2)=4094c2ce9f49730e640b677ebb57dc33427e4517 RIPEMD160(wireshark-1.0.3.tar.bz2)=02714cf78ddc8aefb3506509ceb31d35b4402686 wireshark-1.0.3.tar.gz: 16788553 bytes MD5(wireshark-1.0.3.tar.gz)=a52b0c6c652ce7239bee879cd6ca02f0 SHA1(wireshark-1.0.3.tar.gz)=5b2813de0e30434060a6b91319e4245f43f5da43 RIPEMD160(wireshark-1.0.3.tar.gz)=b05b2faadeee9ce91546474cd99f09d4ba651ecf wireshark-setup-1.0.3.exe: 22201518 bytes MD5(wireshark-setup-1.0.3.exe)=980f7aa115a40d1dd563c39fdc69d55a SHA1(wireshark-setup-1.0.3.exe)=89515d87b44d7d2f9edfc07273f6cc2aae8bb2e2 RIPEMD160(wireshark-setup-1.0.3.exe)=70a79a65a9f5ce15652900f3c0d0eafddbf07999 wireshark-1.0.3.u3p: 20057972 bytes MD5(wireshark-1.0.3.u3p)=602aaf3b410d6d8c83271fc7a787a92e SHA1(wireshark-1.0.3.u3p)=344f28d9f3fa9cab159255b7e74f720413a65e78 RIPEMD160(wireshark-1.0.3.u3p)=246b212ebd30c94eb0514d35e866c27f2550c297 WiresharkPortable-1.0.3.paf.exe: 17505565 bytes MD5(WiresharkPortable-1.0.3.paf.exe)=d52f75ca8c2af2dfdea88fb26b3fe80b SHA1(WiresharkPortable-1.0.3.paf.exe)=0372fcc555da886f629cf17daa2d58766e2243a1 RIPEMD160(WiresharkPortable-1.0.3.paf.exe)=bf131c6bc4bcfad24c798fca752c891b9ff4c35a Wireshark 1.0.3 Intel.dmg: 35849794 bytes MD5(Wireshark 1.0.3 Intel.dmg)=83d0615425d19375b572833ccf38c3b9 SHA1(Wireshark 1.0.3 Intel.dmg)=b65d0e6cd6d0bf2e2157ac8dc1a3590be557132e RIPEMD160(Wireshark 1.0.3 Intel.dmg)=75430dd686b06da7fc3c58b1a9e35270c97434dd patch-wireshark-1.0.2-to-1.0.3.diff.bz2: 94601 bytes MD5(patch-wireshark-1.0.2-to-1.0.3.diff.bz2)=59b98a0668f0af1ae5c95647bc9ed655 SHA1(patch-wireshark-1.0.2-to-1.0.3.diff.bz2)=f2ff84078423c2027574bd68c7ae2fc344ccadae RIPEMD160(patch-wireshark-1.0.2-to-1.0.3.diff.bz2)=77346b4a7fec593ebead8a96fe849399182721a4 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIv2mZpw8IXSHylJoRAr4qAKDOZnRWC1PY8EJJXVAre+YwWBvvUQCgtvvI XKZN092wHsjjgfldeB4gBYs= =1chC -----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-users] How do I use the decryption support in Wireshark?
- Next by Date: Re: [Wireshark-users] Problem running Wireshark on Mac OS X Leopard 10.5.2
- Previous by thread: Re: [Wireshark-users] How do I use the decryption support in Wireshark?
- Next by thread: Re: [Wireshark-users] Problem running Wireshark on Mac OS X Leopard 10.5.2
- Index(es):