Wireshark-users: Re: [Wireshark-users] Wireshark 1.0.9 is now available
Don't you mean 1.2.2?

On Tue, Sep 15, 2009 at 3:48 PM, Gerald Combs <> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'm proud to announce the release of Wireshark 1.0.9.
>
> 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 AFS dissector could crash. (Bug 3564)
>
>       Versions affected: 0.9.2 to 1.0.8, 1.2.0
>
>     o The Infiniband dissector could crash on some platforms.
>
>       Versions affected: 0.9.2 to 1.0.8, 1.2.0
>
>     o The OpcUa dissector could use excessive CPU and memory. (Bug
>       3986)
>
>       Versions affected: 0.99.6 to 1.0.8, 1.2.0 to 1.2.1
>
>   The following bugs have been fixed:
>
>     o Window "capture->Interfaces" cannot be closed. (Bug 1740)
>
>     o Slow response when using Expert Info Composite. (Bug 2504)
>
>     o tshark-1.0.2 (dumpcap) signal abort core saved. (Bug 2767)
>
>     o Crash when applying a display filter. (Bug 3361)
>
>     o Propagate interface Comment field to the Capture... Interfaces
>       dialogue box. (Bug 3414)
>
>     o Crash when searching for Time Reference. (Bug 3429)
>
>     o Wireshark doesn't interpret "adsl" interface in snoop output
>       of Juniper ScreenOS. (Bug 3469)
>
>     o Wireshark start-up very slow when X forwarding over ssh. (Bug
>       3483)
>
>     o Wireshark crashes while reading capture file. (Bug 3489)
>
>     o Windows build with ADNS fails because some ADNS files are
>       missing. (Bug 3499)
>
>     o Field wlan_mgt.fixed.delba.param.initiator is indicated by
>       wrong bit of wlan_mgt.fixed.delba.param. (Bug 3505)
>
>     o Edonkey bug in dissecting UDP Get Gerver Info packets. (Bug
>       3509)
>
>     o The Lucent/Ascend file parser could go into an infinite loop.
>       (Bug 3535)
>
>     o Wireshark crashes when range_string is the data type. (Bug
>       3536)
>
>     o FF Protocol "FMS Initiate - Version OD Calling" field packet
>       data not unpacked properly. (Bug 3694)
>
>  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
>
>   AFS, eDonkey, FTP, IEEE 802.11, Infiniband, ISUP, OpcUa, SCTP
>
>  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.9.tar.bz2: 13394936 bytes
> MD5(wireshark-1.0.9.tar.bz2)=c01c24295645a93aa2c682be55fac866
> SHA1(wireshark-1.0.9.tar.bz2)=32b71e0f38dbb996597fd87e005adc17043bf3ce
> RIPEMD160(wireshark-1.0.9.tar.bz2)=68b4c22339abbe790561789e157ccd2475c6373c
>
> wireshark-1.0.9.tar.gz: 17114396 bytes
> MD5(wireshark-1.0.9.tar.gz)=d7e14eff2ca84f0d7b24335a0bfde5d5
> SHA1(wireshark-1.0.9.tar.gz)=87cc972c0c4b43eb434339812f708b1f8ed85ece
> RIPEMD160(wireshark-1.0.9.tar.gz)=d52412f1de56e4dc88dd133396adb327e409a133
>
> wireshark-setup-1.0.9.exe: 22355464 bytes
> MD5(wireshark-setup-1.0.9.exe)=cfae2bb1229e67a10c8e7b1f557bb30c
> SHA1(wireshark-setup-1.0.9.exe)=7a39dc2f0108cfae2041b9ad9f5b3d155e0ae11a
> RIPEMD160(wireshark-setup-1.0.9.exe)=3323e2050411f3290d24d7f3a7b622161270694e
>
> wireshark-1.0.9.u3p: 20092330 bytes
> MD5(wireshark-1.0.9.u3p)=39bb379a65c671da805d8e6544fee58b
> SHA1(wireshark-1.0.9.u3p)=f1fef3b6c67c959b1f8ea54e3cade195a757c0f8
> RIPEMD160(wireshark-1.0.9.u3p)=1a2e7d988c0a8120e90e07f607f4d9ea4511f1b6
>
> WiresharkPortable-1.0.9.paf.exe: 17517586 bytes
> MD5(WiresharkPortable-1.0.9.paf.exe)=e6f3a31fe344921d3aa65c2ea81df886
> SHA1(WiresharkPortable-1.0.9.paf.exe)=1c00ba6ebb8bd000cca662e746eee3ed70e71918
> RIPEMD160(WiresharkPortable-1.0.9.paf.exe)=a499b97a261aab65ff868400d36aec11acf7aee7
>
> Wireshark 1.0.9 Intel.dmg: 37132286 bytes
> MD5(Wireshark 1.0.9 Intel.dmg)=ce2a03c017910be107aeedee8466ea45
> SHA1(Wireshark 1.0.9 Intel.dmg)=6508be1c7bb9189ae3fc50acd07d0ab8e39e1c8f
> RIPEMD160(Wireshark 1.0.9
> Intel.dmg)=b967712ec39ee5e2b442c4ae555dba9819600b17
>
> Wireshark 1.0.9 PPC.dmg: 38996761 bytes
> MD5(Wireshark 1.0.9 PPC.dmg)=5324d47e4c25ed6538920621835cef70
> SHA1(Wireshark 1.0.9 PPC.dmg)=421f17c29900f7999f1ce36c7e5220eaa25be3b3
> RIPEMD160(Wireshark 1.0.9 PPC.dmg)=19a5f508e7466d59c54518e5ec86fcb4c2328a79
>
> patch-wireshark-1.0.8-to-1.0.9.diff.bz2: 102819 bytes
> MD5(patch-wireshark-1.0.8-to-1.0.9.diff.bz2)=fa0bf860252bb1146ec3641310efcff6
> SHA1(patch-wireshark-1.0.8-to-1.0.9.diff.bz2)=7e23b92300be043c44e9720872d19770edfe1a02
> RIPEMD160(patch-wireshark-1.0.8-to-1.0.9.diff.bz2)=ff872e12233b2e84132126a5bb99bbe4b077caa9
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkqv/YkACgkQpw8IXSHylJosxQCgnVpT6rQqd/z9JH3u49yodAlS
> vncAoMQcNGyJCYi1DtV9SyyRCgVCAfeb
> =yEU9
> -----END PGP SIGNATURE-----
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <[email protected]>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>             mailto:[email protected]?subject=unsubscribe
>