Wireshark · Wireshark-users: Re: [Wireshark-users] Wireshark 1.0.6 is now available

["matt roberts" <k141@xxxxxxxxxxx>]

Thank you for your hard work !!!

Matt.

--------------------------------------------------
From: "Gerald Combs" <gerald@xxxxxxxxxxxxx>
Sent: Friday, February 06, 2009 4:17 PM
To: "Wireshark announcements" <wireshark-announce@xxxxxxxxxxxxx>; "Community 
support list for Wireshark" <wireshark-users@xxxxxxxxxxxxx>; "Developer 
support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx>
Subject: [Wireshark-users] Wireshark 1.0.6 is now available

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'm proud to announce the release of Wireshark 1.0.6.
>
> 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 On non-Windows systems, Wireshark could crash if the HOME
>       environment variable contained sprintf-style string formatting
>       characters. Discovered by babi. (Bug 3150)
>
>       Versions affected: 0.99.8 to 1.0.5
>
>     o Wireshark could crash while reading a malformed NetScreen
>       snoop file. Discovered by babi. (Bug 3151)
>
>       Versions affected: 0.99.7 to 1.0.5
>
>     o Wireshark could crash while reading a Tektronix K12 text
>       capture file. (Bug 1937)
>
>       Versions affected: 0.99.6 to 1.0.5
>
>   The following bugs have been fixed:
>
>     o Crash when loading capture file and Preferences: NO Info
>       column (Bug 2902)
>
>     o Some Lua scripts may lead to corruption via out of bounds
>       stack (Bug 3062)
>
>     o Build with GLib 1.2 fails with error: 'G_MININT32' undeclared
>       (Bug 3109)
>
>     o Wrong decoding IMSI with GSM MAP protocol (Bug 3116)
>
>     o Segmentation fault for "Follow TCP stream" (Bug 3119)
>
>     o SMPP optional parameter 'network_error_code' incorrectly
>       decoded (Bug 3128)
>
>     o DHCPv6 dissector doesn't handle malformed FQDN (Bug 3134)
>
>     o WCCP overrides CFLOW as decoded protocol (Bug 3175)
>
>     o Improper decoding of MPLS echo reply IPv4 Interface and Label
>       Stack Object (Bug 3179)
>
>     o ANSI MAP fix for TRN digits/SMS and OTA subdissection (Bug
>       3214)
>
>     o The 1.0 branch can now be built with Visual Studio 2008.
>
>  New and Updated Features
>
>     o The version of GNUTLS included with the Windows packages has
>       been updated from 2.3.8 to 2.6.3.
>
>  New Protocol Support
>
>   There are no new protocols in this release.
>
>  Updated Protocol Support
>
>   AFS, ATM, DHCPv6, DIS, E.212, RTP, UDP, USB, WCCP, WPS
>
>  New and Updated Capture File Support
>
>   NetScreen snoop
>
> 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.6.tar.bz2: 13161721 bytes
> MD5(wireshark-1.0.6.tar.bz2)=f97041ec73e72fc36e39be2588045578
> SHA1(wireshark-1.0.6.tar.bz2)=1aa726e32905a2815d01a9f33df84a873b11c7ef
> RIPEMD160(wireshark-1.0.6.tar.bz2)=5037c3c5f38c914233f064efb3dbe409896b3e0b
>
> wireshark-1.0.6.tar.gz: 16905873 bytes
> MD5(wireshark-1.0.6.tar.gz)=29cf348676ae237189c13719dcabf858
> SHA1(wireshark-1.0.6.tar.gz)=a1ea81729c23788be3d0eaf8e8e5d22ef132013d
> RIPEMD160(wireshark-1.0.6.tar.gz)=e6801be859045a72e6c07402bd0bbba36f0d9353
>
> wireshark-setup-1.0.6.exe: 22198014 bytes
> MD5(wireshark-setup-1.0.6.exe)=96f32a3d9214550f33232fbcc40c5b62
> SHA1(wireshark-setup-1.0.6.exe)=3cffe6f5c0897519f102ea37bf04038ed07b5ad4
> RIPEMD160(wireshark-setup-1.0.6.exe)=3a9a5e0c64ce8b7e018835f82185062677e073e6
>
> wireshark-1.0.6.u3p: 20028977 bytes
> MD5(wireshark-1.0.6.u3p)=960cc15cff628c7fa571f997ae5aa297
> SHA1(wireshark-1.0.6.u3p)=2c43d14d886ae0e63ca048be6a5100361118f738
> RIPEMD160(wireshark-1.0.6.u3p)=e84eb5c74515a773372eb03f78e14bdab6530a26
>
> WiresharkPortable-1.0.6.paf.exe: 17468003 bytes
> MD5(WiresharkPortable-1.0.6.paf.exe)=d2772bf4891d18d5e03b865eed1e7ac8
> SHA1(WiresharkPortable-1.0.6.paf.exe)=25b18728f174b570f3e4282eeced70d40960e919
> RIPEMD160(WiresharkPortable-1.0.6.paf.exe)=1744a9cfc4c41d37baa0a99323f0ab316b4d48b4
>
> Wireshark 1.0.6 Intel.dmg: 32292604 bytes
> MD5(Wireshark 1.0.6 Intel.dmg)=7de1801931b923f7fffc1d21530dec7e
> SHA1(Wireshark 1.0.6 Intel.dmg)=ef26e389edc662fd687a0933837e96efa3d3ea5c
> RIPEMD160(Wireshark 1.0.6 
> Intel.dmg)=ddd5c998ec7e52bd9bae4db9dfc06bcec1f99619
>
> Wireshark 1.0.6 PPC.dmg: 34726228 bytes
> MD5(Wireshark 1.0.6 PPC.dmg)=d22d971cb3b552315f410326bd317c23
> SHA1(Wireshark 1.0.6 PPC.dmg)=bc1b58822660a74d2424215f379abf5610e0072b
> RIPEMD160(Wireshark 1.0.6 
> PPC.dmg)=66193f2c73b928b83a39f72706de2515e668d353
>
> patch-wireshark-1.0.5-to-1.0.6.diff.bz2: 99151 bytes
> MD5(patch-wireshark-1.0.5-to-1.0.6.diff.bz2)=99bfdc39ba2701cc24c991f68b633ccc
> SHA1(patch-wireshark-1.0.5-to-1.0.6.diff.bz2)=5f6830eef9ad8dd5a76fdc7b9a8ec2274ee00389
> RIPEMD160(patch-wireshark-1.0.5-to-1.0.6.diff.bz2)=711df2235284b1b2ce586cee6722ee55adb6e97e
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Darwin)
>
> iEYEARECAAYFAkmM0yAACgkQpw8IXSHylJoRyQCcCbu5+Xbd0oIaNuLQYbO0zDor
> P00An3/qBspQbGGU5GOhNYMpOlW3hpTm
> =WEAx
> -----END PGP SIGNATURE-----
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe