Wireshark-users: Re: [Wireshark-users] Wireshark 1.0.1 is now available
From: "Lars Ruoff" <lars.ruoff@xxxxxxxxxxxxxxxxx>
Date: Tue, 1 Jul 2008 12:11:36 +0200
Hi Gerald, The link entitled "Get Wireshark Now - 1.0.1 for Windows" gets me to a ""wireshark-setup-1.0.0.exe" download. ??? Br, Lars > -----Original Message----- > From: wireshark-users-bounces@xxxxxxxxxxxxx > [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of > Gerald Combs > Sent: mardi 1 juillet 2008 01:40 > To: Wireshark announcements; Community support list for > Wireshark; Developer support list for Wireshark > Subject: [Wireshark-users] Wireshark 1.0.1 is now available > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I'm proud to announce the release of Wireshark 1.0.1. > > 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 GSM SMS dissector could crash. > > Versions affected: 0.99.2 to 1.0.0 > > o The PANA and KISMET dissectors could force Wireshark to quit > unexpectedly. > > Versions affected: 0.99.3 to 1.0.0 > > o The RTMPT dissector could crash. > > Versions affected: 0.99.8 to 1.0.0 > > o The RMI dissector could disclose system memory. Discovered by > Noam Rathus. > > Versions affected: 0.9.5 to 1.0.0 > > o The syslog dissector could crash. > > Versions affected: 1.0.0 > > The following bugs have been fixed: > > o RPC portmap classification switched to TCP after filtering. > (Bug 1392) > > o Force the foreground color when the background is forced. (Bug > 1735) > > o RPC stream shows malformed packets. (Bug 2148) > > o SNMP trap dissection fails. (Bug 2253) > > o Failure to detect/open valid ERF files. (Bug 2359) > > o Window scaling bug. (Bug 2378) > > o Bugs in the EIGRP dissector. (Bug 2381) > > o E212 Mobile network code 3rd digit is not correctly decoded. > (Bug 2393) > > o The BOOTP dissector fails to initialize and display some > values. (Bug 2395) > > o Data string filter crash. (Bug 2402) > > o Debian packaging problems. (Bug 2405) > > o Expert info composite crash for LDAP. (Bug 2407) > > o Statistics > Multicast Streams are broken. (Bug 2414) > > o "Read me first" file is empty in the OS X .dmg. (Bug 2425) > > o Failed tshark PDML export to file. (Bug 2432) > > o RTCP MOS fields display wrong values. (Bug 2440) > > o SNMP trap parse error. (Bug 2442) > > o Ports incorrectly decoded as DPLAY instead of RTP. (Bug 2452) > > o Incorrect decoding of DST MAC address of frame containing > ICMPv6 Echo Request. (Bug 2456) > > o Fix wireshark-filter man page for packet-diameter_3gpp.c > fields. (Bug 2457) > > o Dissector bug, protocol SNMP: proto.c:932: failed assertion. > (Bug 2468) > > o UDP not decoded as UNIStim. (Bug 2475) > > o Debug text output from MIKEY dissector. (Bug 2481) > > o Windows compilation errors with flex 2.5.35. (Bug 2493) > > o RTP heuristic interferes with STUN/T38 portion of heuristic. > (Bug 2497) > > o WiMAX dissector assertion. (Bug 2501) > > o RTP header extensions with length>4 bytes dissected > incorrectly. (Bug 2505) > > o Compilation failure on non-european Windows systems. (Bug > 2513) > > o BACnet BVLC NAK decoding. (Bug 2517) > > o 'tshark -Tfields -e data' omits last character of data. (Bug > 2518) > > o "Next file every" inconsistent behaviour. (Bug 2599) > > o Wireshark doest not parse iSCSI login PDU. (Bug 2616) > > o URL and encoding for OUI listings in make-manuf. (Bug 2619) > > New and Updated Features > > The following features are new (or have been significantly > updated) since the last release: > > o The "About" box finally displays version 1.0. > > o Wireshark now supports custom columns. > > o This release includes an experimental Mac OS X package. > > New Protocol Support > > There are no new protocols in this release. > > Updated Protocol Support > > ACTRACE, BACnet BVLC, BOOTP, E212, iSCSI, IUA, LDAP, MGCP, MIKEY, > MSMMS, RMI, RPC, RTCP, RTP, SIP, SNMP, TCP, UNIStim, WiMAX > > New and Updated Capture File Support > > Endace ERF > > 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) > > Wireshark is unable to decrypt WPA group keys. (Bug 1420) > > 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.1.tar.bz2: 13087502 bytes > MD5(wireshark-1.0.1.tar.bz2)=e1a0c8402622b8416fcf8ccf429a115f > SHA1(wireshark-1.0.1.tar.bz2)=828efc186bc7eb4872628952598cd38389d8d5b0 > RIPEMD160(wireshark-1.0.1.tar.bz2)=2e53cfda4cd7b831c19463ebfa8 8c74cb625b1a1 > > MD5(wireshark-1.0.1.tar.gz)=da33c2abeb8b982ca50e4c43d8c0fe27 > SHA1(wireshark-1.0.1.tar.gz)=b178f3539759966d86f7f2e423cbf26067fe1134 > RIPEMD160(wireshark-1.0.1.tar.gz)=469c329285d7a30cb6da0df241a0 2c35e237de2c > > wireshark-setup-1.0.1.exe: 22212707 bytes > MD5(wireshark-setup-1.0.1.exe)=63aeef697893d1562eee98e528b762e6 > SHA1(wireshark-setup-1.0.1.exe)=a2854e5b194d153aa2fd14d075bc63 adc1c4af1e > RIPEMD160(wireshark-setup-1.0.1.exe)=c408f044c2baacf72cbceabb9 6e91f8c1229341e > > wireshark-1.0.1.u3p: 20048751 bytes > MD5(wireshark-1.0.1.u3p)=ea27534e619fb4366c9ceeff4d93fcaf > SHA1(wireshark-1.0.1.u3p)=7e1e75f8a3f28d4f722a794ee00aa56ab67ee9bd > RIPEMD160(wireshark-1.0.1.u3p)=0a5b8bad236420b0a7afa1be172b3b2 c2bea5e99 > > WiresharkPortable-1.0.1.paf.exe: 17496035 bytes > MD5(WiresharkPortable-1.0.1.paf.exe)=ccaa4338c66e68505efecd4ca28b837d > SHA1(WiresharkPortable-1.0.1.paf.exe)=d56fb6c403ae59cc56eb2bd1 > 3b5d7f46d065660c > RIPEMD160(WiresharkPortable-1.0.1.paf.exe)=73669d7a18996392f39 ba02ff56f0f88b4cae53c > > Wireshark 1.0.1 Intel.dmg: 35834540 bytes MD5(Wireshark 1.0.1 > Intel.dmg)=4696b65e6d37862963d8a531e7e47ad9 > SHA1(Wireshark 1.0.1 > Intel.dmg)=e41ad6f21d3a4e24df1071c35347ed8a1de03450 > RIPEMD160(Wireshark 1.0.1 > Intel.dmg)=aa531409ad8d7f3a3b3b0b65e790061e1c5a69ea > > patch-wireshark-1.0.0-to-1.0.1.diff.bz2: 138218 bytes > MD5(patch-wireshark-1.0.0-to-1.0.1.diff.bz2)=2c1b5044691686bf9 a103e975d7cc3c1 > SHA1(patch-wireshark-1.0.0-to-1.0.1.diff.bz2)=6279766ab8f9efe7 dc61bbb6a162ea30ea2c72a9 > RIPEMD160(patch-wireshark-1.0.0-to-1.0.1.diff.bz2)=e814b45c475 b943dbc1242107324386cedcf5090 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.8 (Darwin) > > iEYEARECAAYFAkhpbuQACgkQpw8IXSHylJphvgCfcori//vF1JVGjLLPwCGftT9r > XiwAoMwNQEAJIJS8N/tkwaoQyB6O9T7+ > =o7Cl > -----END PGP SIGNATURE----- > _______________________________________________ > Wireshark-users mailing list > Wireshark-users@xxxxxxxxxxxxx > https://wireshark.org/mailman/listinfo/wireshark-users
- Follow-Ups:
- Re: [Wireshark-users] Wireshark 1.0.1 is now available
- From: Gerald Combs
- Re: [Wireshark-users] Wireshark 1.0.1 is now available
- Prev by Date: [Wireshark-users] how to print time with epoch formation by tshark
- Next by Date: Re: [Wireshark-users] Bug 553: Wireshark appears offscreen on multi-monitor Windows systems (Was: Wireshark 1.0.1 is now available)
- Previous by thread: Re: [Wireshark-users] how to print time with epoch formation by tshark
- Next by thread: Re: [Wireshark-users] Wireshark 1.0.1 is now available
- Index(es):