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

[M K <gedropi@xxxxxxxxx>]

Suggestions for W2000 SP4 OED?  Currently using 1.0.9.
On 6/10/10, Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> wrote:
> It supports some older systems not supported by 1.2.  For example, the
> 1.0 versions are the last versions that can work with GTK 1.  I think it
> may also be the last version that runs on Windows 98(?).
>
> Luke.Wilson-Stepan@xxxxxxxxxxxxxxxxx wrote:
>> 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.
> ___________________________________________________________________________
> 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
>