path: root/docbook/release-notes.xml

<?xml version="1.0"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

<!-- $Id$ -->

<!--
DOCUMENT SECTION
-Use this section to encode all document information
-->

<!--
Wireshark Info
-->

  <!ENTITY WiresharkCurrentVersion "1.2.17">

]>

<article>
  <title>Wireshark &WiresharkCurrentVersion; Release Notes</title>

  <section id="WhatIs"><title>What is Wireshark?</title>
    <para>
      Wireshark is the world's most popular network protocol analyzer.  It
      is used for troubleshooting, analysis, development, and education.
    </para>
  </section>

  <section id="WhatsNew"><title>What's New</title>
    <section id="BugFixes"><title>Bug Fixes</title>

    <para>

      The following vulnerabilities have been fixed. See the
      <ulink url="http://www.wireshark.org/security/wnpa-sec-2011-07.html">security advisory</ulink> for details and a workaround.

      <itemizedlist>

        <listitem>
          <para>
            Large/infinite loop in the DICOM dissector.
            <!-- Fixed in trunk: r36958 -->
            <!-- Fixed in trunk-1.4: r????? -->
            <!-- Fixed in trunk-1.2: r37213 -->
            (<ulink url="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5876">Bug
            5876</ulink>)
          </para>
          <para>Versions affected: 1.2.0 to 1.2.16 and 1.4.0 to 1.4.6.</para>
<!--
          <para>
            <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-????">CVE-2010-????</ulink>
          </para>
-->
        </listitem>

        <listitem>
          <para>
            Huzaifa Sidhpurwala of the Red Hat Security Response Team discovered
            that a corrupted Diameter dictionary file could crash Wireshark.
            <!-- Fixed in trunk: r37011 -->
            <!-- Fixed in trunk-1.4: r????? -->
            <!-- Fixed in trunk-1.2: r37213 -->
          </para>
          <para>Versions affected: 1.2.0 to 1.2.16 and 1.4.0 to 1.4.6.</para>
<!--
          <para>
            <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-????">CVE-2010-????</ulink>
          </para>
-->
        </listitem>

        <listitem>
          <para>
            Huzaifa Sidhpurwala of the Red Hat Security Response Team discovered
            that a corrupted snoop file could crash Wireshark.
            <!-- Fixed in trunk: r37068 -->
            <!-- Fixed in trunk-1.4: r????? -->
            <!-- Fixed in trunk-1.2: r37213 -->
          </para>
          <para>Versions affected: 1.2.0 to 1.2.16 and 1.4.0 to 1.4.6.</para>
<!--
          <para>
            <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-????">CVE-2010-????</ulink>
          </para>
-->
        </listitem>

        <listitem>
          <para>
            David Maciejak of Fortinet's FortiGuard Labs discovered that
            malformed compressed capture data could crash Wireshark.
            <!-- Fixed in trunk: r37081 -->
            <!-- Fixed in trunk-1.4: r????? -->
            <!-- Fixed in trunk-1.2: r37213 -->
            (<ulink url="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5908">Bug
            5908</ulink>)
          </para>
          <para>Versions affected: 1.2.0 to 1.2.16 and 1.4.0 to 1.4.6.</para>
<!--
          <para>
            <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-????">CVE-2010-????</ulink>
          </para>
-->
        </listitem>

        <listitem>
          <para>
            Huzaifa Sidhpurwala of the Red Hat Security Response Team discovered
            that a corrupted Visual Networks file could crash Wireshark.
            <!-- Fixed in trunk: r37128 -->
            <!-- Fixed in trunk-1.4: r????? -->
            <!-- Fixed in trunk-1.2: r37213 -->
            (<ulink url="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5934">Bug
            5934</ulink>)
          </para>
          <para>Versions affected: 1.2.0 to 1.2.16 and 1.4.0 to 1.4.6.</para>
<!--
          <para>
            <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-????">CVE-2010-????</ulink>
          </para>
-->
        </listitem>

      </itemizedlist>

    </para>

    <para>
    The following bugs have been fixed:

      <itemizedlist>

<!--
        <listitem><para>
          Wireshark will go all Weezer on you and destroy your sweater.
          (<ulink url="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=0000">Bug
          0000</ulink>)
        </para></listitem>
-->

      </itemizedlist>

    </para>

    </section>

    <section id="NewFeatures"><title>New and Updated Features</title>
    <para>

There are no new features in this release.

    </para>
    </section>

    <section id="NewProtocols"><title>New Protocol Support</title>
    <para>

There are no new protocols in this release.

    </para>
    </section>

    <section id="UpdatedProtocols"><title>Updated Protocol Support</title>
    <para>


    </para>
    </section>

    <section id="NewCapture"><title>Updated Capture File Support</title>
    <para>

There are no capture file support updates in this release.

    </para>
    </section>

  </section>

  <section id="GettingWireshark"><title>Getting Wireshark</title>
    <para>
      Wireshark source code and installation packages are available from
      <ulink url="http://www.wireshark.org/download.html">http://www.wireshark.org/download.html</ulink>.
    </para>

    <section id="VendorPackages"><title>Vendor-supplied Packages</title>
      <para>
	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
	<ulink url="http://www.wireshark.org/download.html#thirdparty">download page</ulink> on the Wireshark web site.
      </para>
    </section>

  </section>

  <!-- XXX needs to be written
  <section id="RemovingWireshark"><title>Removing Wireshark</title>
    <para>
    </para>
  </section>
  -->

  <section id="FileLocations"><title>File Locations</title>
    <para>
      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.
    </para>
  </section>

  <section id="KnownProblems"><title>Known Problems</title>

    <para>
      Wireshark might make your system disassociate from a wireless network
      on OS X.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1315">Bug
      1315</ulink>)
    </para>

    <para>
      Dumpcap might not quit if Wireshark or TShark crashes.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419">Bug
      1419</ulink>)
    </para>

    <para>
      The BER dissector might infinitely loop.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516">Bug
      1516</ulink>)
    </para>

    <para>
      Capture filters aren't applied when capturing from named pipes.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814">Bug
      1814</ulink>)
    </para>

    <para>
      Wireshark might freeze when reading from a pipe.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2082">Bug
      2082</ulink>)
    </para>

    <para>
      Filtering tshark captures with display filters (-R) no longer works.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234">Bug
      2234</ulink>)
    </para>

    <para>
      The 64-bit Windows installer does not ship with the same libraries as the
      32-bit installer.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3610">Bug
      3610</ulink>)
    </para>

    <para>
      Wireshark will not run on Windows 2000.
      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5874">Bug
      5874</ulink>)
    </para>

  </section>

  <section id="GettingHelp"><title>Getting Help</title>
    <para>
    Community support is available on
    <ulink url="http://ask.wireshark.org/">Wireshark's Q&amp;A site</ulink>
    and on the wireshark-users mailing list.
    Subscription information and archives for all of Wireshark's mailing
    lists can be found on <ulink url="http://www.wireshark.org/lists/">the
    web site</ulink>.
    </para>
    <para>
    Training is available from
    <ulink url="http://www.wiresharktraining.com/">Wireshark University</ulink>.
    </para>
  </section>

  <section id="FAQ"><title>Frequently Asked Questions</title>
    <para>
    A complete FAQ is available on the
    <ulink url="http://www.wireshark.org/faq.html">Wireshark web site</ulink>.
    </para>
  </section>

</article>