Wireshark-users: Re: [Wireshark-users] Wireshark 1.0.14 is now available
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: <Luke.Wilson-Stepan@xxxxxxxxxxxxxxxxx>
Date: Thu, 10 Jun 2010 08:36:24 -0500
What is this "old stable" release for, anyway?  I can't find anything
online explaining its purpose.

Luke Wilson-Stepan


                                                                                                                       
  From:       "Gerald Combs" <gerald@xxxxxxxxxxxxx>                                                                    
                                                                                                                       
  To:         wireshark-announce@xxxxxxxxxxxxx, "Community support list for Wireshark"                                 
              <wireshark-users@xxxxxxxxxxxxx>, "Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx>    
                                                                                                                       
  Date:       06/09/2010 04:37 PM                                                                                      
                                                                                                                       
  Subject:    [Wireshark-users] Wireshark 1.0.14 is now available                                                      
                                                                                                                       
  Sent by:    wireshark-users-bounces@xxxxxxxxxxxxx                                                                    
                                                                                                                       





-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wireshark 1.0.14 is now available.


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 dissector could dereference a NULL pointer. (Bug 4734)

       Versions affected: 0.99.6 to 1.0.13, 1.2.0 to 1.2.8

     o J. Oquendo discovered that the ASN.1 BER dissector could
       overrun the stack.

       Versions affected: 0.10.13 to 1.0.13, 1.2.0 to 1.2.8

     o The SMB PIPE dissector could dereference a NULL pointer on
       some platforms.

       Versions affected: 0.8.20 to 1.0.13, 1.2.0 to 1.2.8

     o The SigComp Universal Decompressor Virtual Machine could go
       into an infinite loop. (Bug 4826)

       Versions affected: 0.10.7 to 1.0.13, 1.2.0 to 1.2.8

     o The SigComp Universal Decompressor Virtual Machine could
       overrun a buffer. (Bug 4837)

       Versions affected: 0.10.8 to 1.0.13, 1.2.0 to 1.2.8

   The following bugs have been fixed:

     o Cannot open file with File -> Open. (Bug 1791)

     o Fedora 13: wireshark fails to build (linking problem). (Bug
       4815)

  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

   ASN.1 BER, SMB, SMB PIPE

  New and Updated Capture File Support

   There is no new or updated capture file support.

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.14.tar.bz2: 13451088 bytes
MD5(wireshark-1.0.14.tar.bz2)=8b6ece0c52b7d8b35cca8d9059340004
SHA1(wireshark-1.0.14.tar.bz2)=a950141e224dce4faac749196452c6eecc402193
RIPEMD160
(wireshark-1.0.14.tar.bz2)=128f0e2beea9dbe3794f2f9eb043d6c1ff06568f

wireshark-1.0.14.tar.gz: 17191234 bytes
MD5(wireshark-1.0.14.tar.gz)=35930f6f2dcc8698bb13ed30b64e234d
SHA1(wireshark-1.0.14.tar.gz)=13fca4d6a662628ee7d80630ca67d0b080b56145
RIPEMD160(wireshark-1.0.14.tar.gz)=84aca6f281cc0bb2ca185f42af11b5e5cc788075

wireshark-setup-1.0.14.exe: 22497551 bytes
MD5(wireshark-setup-1.0.14.exe)=de561d398463863567d24f2f081dc825
SHA1(wireshark-setup-1.0.14.exe)=91abc2ad09e9925c1b8620f2e944e4e58a2c5682
RIPEMD160
(wireshark-setup-1.0.14.exe)=6864355eb08c91574a649b079ded76b996cc6cb9

wireshark-1.0.14.u3p: 20172784 bytes
MD5(wireshark-1.0.14.u3p)=6d9f4e554744df414a382818a1f8c0c6
SHA1(wireshark-1.0.14.u3p)=627cbda5e90f794803c1dcc2f00b873770b4ec3e
RIPEMD160(wireshark-1.0.14.u3p)=2c864cf98b07b11ec6b12f22f5256006fd46058e

WiresharkPortable-1.0.14.paf.exe: 17588952 bytes
MD5(WiresharkPortable-1.0.14.paf.exe)=750e0e01e39a37f6a850165ad2945f73
SHA1
(WiresharkPortable-1.0.14.paf.exe)=07bdf75c03260cbadcedade650a750a0354047d8
RIPEMD160
(WiresharkPortable-1.0.14.paf.exe)=2441f77e703a8d628538b71c90141db02f3094db

Wireshark 1.0.14 Intel.dmg: 37217508 bytes
MD5(Wireshark 1.0.14 Intel.dmg)=9fb485c0ff7a8de93028c88493e3b30c
SHA1(Wireshark 1.0.14 Intel.dmg)=c107cfe5adf0cbf5ebc8d87dbb39022821343b42
RIPEMD160(Wireshark 1.0.14
Intel.dmg)=9db47632e80fd8a815e6e7d36c6ef3b4991cf1ac

Wireshark 1.0.14 PPC.dmg: 39108557 bytes
MD5(Wireshark 1.0.14 PPC.dmg)=7624f2264d565d8d1997c704ad74ab26
SHA1(Wireshark 1.0.14 PPC.dmg)=eb25f5b30bcf79a135587bf8b96047abbffc5161
RIPEMD160(Wireshark 1.0.14
PPC.dmg)=269c5f90089ef6ed1012f14eedfd689f1fc4968e

patch-wireshark-1.0.13-to-1.0.14.diff.bz2: 35582 bytes
MD5
(patch-wireshark-1.0.13-to-1.0.14.diff.bz2)=4ff25be01c39d857a11e17ec4b1378c0

SHA1
(patch-wireshark-1.0.13-to-1.0.14.diff.bz2)=8ac80e3fe5476e42bc6481fd25bc94d6db12c3c2

RIPEMD160
(patch-wireshark-1.0.13-to-1.0.14.diff.bz2)=fbfcf716b703b3397ae98540b13fcb8698ab259c

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

iEYEARECAAYFAkwQCF0ACgkQpw8IXSHylJrBOgCeO1tCnoY2zCFNex1fnzB+uvdt
T34An2kSVUG1Dmf7QhmmO/BkwnCC1loR
=/xiu
-----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





This e-mail and any files transmitted with it are confidential and are solely for the use of the addressee.  It may contain material that is legally privileged, proprietary or subject to copyright belonging to Mutual of Omaha Insurance Company and its affiliates, and it may be subject to protection under federal or state law.  If you are not the intended recipient, you are notified that any use of this material is strictly prohibited.  If you received this transmission in error, please contact the sender immediately by replying to this e-mail and delete the material from your system.  Mutual of Omaha Insurance Company may archive e-mails, which may be accessed by authorized persons and may be produced to other parties, including public authorities, in compliance with applicable laws.