Wireshark-announce: [Wireshark-announce] Wireshark 1.0.11 is now available

Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>
Date: Wed, 27 Jan 2010 16:35:00 -0800
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm proud to announce the release of Wireshark 1.0.11.

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 SMB and SMB2 dissectors could crash. (Bug 4301)

       Versions affected: 0.9.0 to 1.0.10, 1.2.0 to 1.2.4

       CVE-2009-4377

     o The Infiniband dissector could crash on some platforms.

       Versions affected: 1.0.6 to 1.0.10, 1.2.0

       CVE-2009-2563

     o Babi discovered several buffer overflows in the LWRES
       dissector.

       Versions affected: 0.9.15 to 1.0.10, 1.2.0 to 1.2.5

   The following bugs have been fixed:

     o Wireshark locks up some Windows 2000 systems. (Bug 3270)

  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

   Infiniband, Kerberos, LWRES, SMB, SMB2

Getting Wireshark

   Wireshark source code and installation packages are available from
   http://www.wireshark.org/download.html.

  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.11.tar.bz2: 13426263 bytes
MD5(wireshark-1.0.11.tar.bz2)=16621db23a243338d749c86c61484788
SHA1(wireshark-1.0.11.tar.bz2)=7adababd1c9d18dd6d235e4eb8fc064f5119514b
RIPEMD160(wireshark-1.0.11.tar.bz2)=edb060c4eb7089f4d82e80cc28762b6f75caee37

wireshark-1.0.11.tar.gz: 17133836 bytes
MD5(wireshark-1.0.11.tar.gz)=c3dc1541b32656fc9a8edd3605c4998f
SHA1(wireshark-1.0.11.tar.gz)=d73f292d6202025b33106a2180847a1f323afde8
RIPEMD160(wireshark-1.0.11.tar.gz)=9c7ec3790469c9b21f45e2046429ba3737e1bca7

wireshark-setup-1.0.11.exe: 22398734 bytes
MD5(wireshark-setup-1.0.11.exe)=f329e1f1a9a7a9dbda7d56c2e98d6a42
SHA1(wireshark-setup-1.0.11.exe)=81a1ccd82a35695b4f795a2ac3de6b3c888417aa
RIPEMD160(wireshark-setup-1.0.11.exe)=0625fa4676db8e2ec4d6d998e3679fea7fb7a8c3

wireshark-1.0.11.u3p: 20150593 bytes
MD5(wireshark-1.0.11.u3p)=e336c588b25c4a7d3f9dcd59a99cea21
SHA1(wireshark-1.0.11.u3p)=ca862b75412f269cd7d5395ce65d6471eb86d51d
RIPEMD160(wireshark-1.0.11.u3p)=ec0ddf07b16302b34209b2c6f57431a4e915a03d

WiresharkPortable-1.0.11.paf.exe: 17570145 bytes
MD5(WiresharkPortable-1.0.11.paf.exe)=f5c7043a424cf3c26db19830f8441572
SHA1(WiresharkPortable-1.0.11.paf.exe)=944d7db17735bd77bbe387ce16f86b22504910c5
RIPEMD160(WiresharkPortable-1.0.11.paf.exe)=54ad934371a36853aef57c85353cae1bfae9cadc

Wireshark 1.0.11 Intel.dmg: 37173604 bytes
MD5(Wireshark 1.0.11 Intel.dmg)=8b88756003ea258da3d8950fa7be413c
SHA1(Wireshark 1.0.11 Intel.dmg)=232c0798fa03a8a8676bfe4e48506ea3c3dcf22a
RIPEMD160(Wireshark 1.0.11
Intel.dmg)=c8f9ff9d8107067d087b4d63c0222ae55bdc1691

Wireshark 1.0.11 PPC.dmg: 39051238 bytes
MD5(Wireshark 1.0.11 PPC.dmg)=6df8632df17faea0bf1fd41253175a34
SHA1(Wireshark 1.0.11 PPC.dmg)=5c0586777fc2e55ef5b2dd2d770322fdcbe0b9cd
RIPEMD160(Wireshark 1.0.11 PPC.dmg)=b830cad572993ff5c9caf33f483d226571d3ddde

patch-wireshark-1.0.10-to-1.0.11.diff.bz2: 570118 bytes
MD5(patch-wireshark-1.0.10-to-1.0.11.diff.bz2)=a8af5ca15b08e5fc781b2b68d49f0129
SHA1(patch-wireshark-1.0.10-to-1.0.11.diff.bz2)=1e3f00443794249fdcb995292d9b33b0f5d678d3
RIPEMD160(patch-wireshark-1.0.10-to-1.0.11.diff.bz2)=5b24f0734d92c4bead55ff2d75d470f32560488c

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktg27QACgkQpw8IXSHylJoTqQCaA671l81w4jO/TLEY6KCzRU+2
7CEAn12yygv4qyZdzq+J6wv6yPskcEsA
=aL0G
-----END PGP SIGNATURE-----