1.3.3 -> 1.3.4.
[obnox/wireshark/wip.git] / docbook / release-notes.xml
index a553ee9044f15b9a9c719d559ed9f0f2db1f0f04..2d622af78199b3bc8ab3e363f5178c53069f50fb 100644 (file)
@@ -12,7 +12,7 @@ DOCUMENT SECTION
 <!--
 Wireshark Info
 -->
-  <!ENTITY WiresharkCurrentVersion "0.99.7">
+  <!ENTITY WiresharkCurrentVersion "1.3.4">
 
 ]>
 
@@ -27,7 +27,7 @@ Wireshark Info
   </section>
 
   <section id="WhatsNew"><title>What's New</title>
-    <section><title>Bug Fixes</title>
+    <section id="BugFixes"><title>Bug Fixes</title>
     <para>
 
       The following vulnerabilities have been fixed.  See the
@@ -37,23 +37,12 @@ Wireshark Info
 
         <listitem>
           <para>
-            Wireshark could crash when reading an MP3 file.
-            <!-- Fixed in r22261 -->
-            <!-- (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=???">???</ulink>) -->
+            The NetFlow dissector could run off with your dog, crash your truck,
+            and write a country music song about the experience.
+            <!-- Fixed in r????? -->
+            <!-- (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=????">????</ulink>) -->
           </para>
-          <para>Versions affected: 0.99.6</para>
-          <para>
-            <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-           Beyond Security discovered that Wireshark could loop
-           excessively while reading a malformed DNP packet.
-            <!-- Fixed in r22811 -->
-          </para>
-          <para>Versions affected: 0.10.12 to 0.99.6</para>
+          <para>Versions affected: 0.99.5 to 1.0.8</para>
           <para>
             <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
           </para>
@@ -67,27 +56,61 @@ Wireshark Info
 
     The following bugs have been fixed:
 
+      <itemizedlist>
+
+        <listitem><para>
+            Wireshark could crash without warning.
+        </para></listitem>
+
+      </itemizedlist>
+
     </para>
 
     </section>
 
-    <section><title>New and Updated Features</title>
+    <section id="NewFeatures"><title>New and Updated Features</title>
     <para>
       The following features are new (or have been significantly updated)
-      since the last release:
+      since version 1.2:
 
       <itemizedlist>
 
         <listitem>
           <para>
-            Most of the capture code has been moved out of the GUI, which
-            means that Wireshark no longer needs to be run as root.
+            The packet list internals have been rewritten and are now more
+            efficient.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Python scripting support has been added.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Capturing from pipes on Windows has been improved.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Many memory leaks have been fixed.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            You can now filter directly on SNMP OIDs.
+           Wireshark no longer supports Windows 2000. Please use
+           Wireshark 1.2 or 1.0 on those systems.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Packtets can now be ignored (excluded from dissection), similar to
+            the way they can be marked.
           </para>
         </listitem>
 
@@ -96,18 +119,18 @@ Wireshark Info
     </para>
     </section>
 
-    <section><title>New Protocol Support</title>
+    <section id="NewProtocols"><title>New Protocol Support</title>
     <para>
 
     </para>
     </section>
 
-    <section><title>Updated Protocol Support</title> <para>
+    <section id="UpdatedProtocols"><title>Updated Protocol Support</title> <para>
 
     </para>
     </section>
 
-    <section><title>New and Updated Capture File Support</title>
+    <section id="NewCapture"><title>New and Updated Capture File Support</title>
     <para>
 
     </para>
@@ -118,11 +141,10 @@ Wireshark Info
   <section id="GettingWireshark"><title>Getting Wireshark</title>
     <para>
       Wireshark source code and installation packages are available from
-      the <ulink url="http://www.wireshark.org/download.html">download
-      page</ulink> on the main web site.
+      <ulink url="http://www.wireshark.org/download.html">http://www.wireshark.org/download.html</ulink>.
     </para>
 
-    <section><title>Vendor-supplied Packages</title>
+    <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
@@ -153,10 +175,73 @@ Wireshark Info
   <section id="KnownProblems"><title>Known Problems</title>
 
     <para>
-      The <guibutton>Filter</guibutton> button is nonfunctional in the
-      file dialogs under Windows.
-      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=942">Bug
-      942</ulink>)
+      Wireshark may appear offscreen on multi-monitor Windows systems.
+      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553">Bug
+      553</ulink>)
+    </para>
+
+    <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>
+      Wireshark is unable to decrypt WPA group keys.
+      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1420">Bug
+      1420</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>
+      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.
+      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1605">Bug
+      1605</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>
+      Capturing from named pipes might be delayed on Windows.
+      (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2200">Bug
+      2200</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>
 
   </section>