docbook/release-notes.xml

   1 <?xml version="1.0"?>
   2 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
   3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
   4
   5 <!-- $Id$ -->
   6
   7 <!--
   8 DOCUMENT SECTION
   9 -Use this section to encode all document information
  10 -->
  11
  12 <!--
  13 Wireshark Info
  14 -->
  15   <!ENTITY WiresharkCurrentVersion "1.3.0">
  16
  17 ]>
  18
  19 <article>
  20   <title>Wireshark &WiresharkCurrentVersion; Release Notes</title>
  21
  22   <section id="WhatIs"><title>What is Wireshark?</title>
  23     <para>
  24       Wireshark is the world's most popular network protocol analyzer.  It
  25       is used for troubleshooting, analysis, development, and education.
  26     </para>
  27   </section>
  28
  29   <section id="WhatsNew"><title>What's New</title>
  30     <section id="BugFixes"><title>Bug Fixes</title>
  31     <para>
  32
  33       The following vulnerabilities have been fixed.  See the
  34       <ulink url="http://www.wireshark.org/security/wnpa-sec-2007-02.html">security advisory</ulink> for details and a workaround.
  35
  36       <itemizedlist>
  37
  38         <listitem>
  39           <para>
  40             The NetFlow dissector could run off with your dog, crash your truck,
  41             and write a country music song about the experience.
  42             <!-- Fixed in r????? -->
  43             <!-- (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=????">????</ulink>) -->
  44           </para>
  45           <para>Versions affected: 0.99.5 to 1.0.8</para>
  46           <para>
  47             <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
  48           </para>
  49         </listitem>
  50
  51       </itemizedlist>
  52
  53     </para>
  54
  55     <para>
  56
  57     The following bugs have been fixed:
  58
  59       <itemizedlist>
  60
  61         <listitem><para>
  62             Wireshark could crash without warning.
  63         </para></listitem>
  64
  65       </itemizedlist>
  66
  67     </para>
  68
  69     </section>
  70
  71     <section id="NewFeatures"><title>New and Updated Features</title>
  72     <para>
  73       The following features are new (or have been significantly updated)
  74       since version 1.2:
  75
  76       <itemizedlist>
  77
  78         <listitem>
  79           <para>
  80             The packet list internals have been rewritten and are now more
  81             efficient.
  82           </para>
  83         </listitem>
  84
  85         <listitem>
  86           <para>
  87             Python scripting support has been added.
  88           </para>
  89         </listitem>
  90
  91         <listitem>
  92           <para>
  93             Capturing from pipes on Windows has been improved.
  94           </para>
  95         </listitem>
  96
  97       </itemizedlist>
  98
  99     </para>
 100     </section>
 101
 102     <section id="NewProtocols"><title>New Protocol Support</title>
 103     <para>
 104
 105     </para>
 106     </section>
 107
 108     <section id="UpdatedProtocols"><title>Updated Protocol Support</title> <para>
 109
 110     </para>
 111     </section>
 112
 113     <section id="NewCapture"><title>New and Updated Capture File Support</title>
 114     <para>
 115
 116     </para>
 117     </section>
 118
 119   </section>
 120
 121   <section id="GettingWireshark"><title>Getting Wireshark</title>
 122     <para>
 123       Wireshark source code and installation packages are available from
 124       the <ulink url="http://www.wireshark.org/download.html">download
 125       page</ulink> on the main web site.
 126     </para>
 127
 128     <section id="VendorPackages"><title>Vendor-supplied Packages</title>
 129       <para>
 130         Most Linux and Unix vendors supply their own Wireshark packages.
 131         You can usually install or upgrade Wireshark using the package management
 132         system specific to that platform.  A list of third-party packages
 133         can be found on the
 134         <ulink url="http://www.wireshark.org/download.html#otherplat">download page</ulink> on the Wireshark web site.
 135       </para>
 136     </section>
 137
 138   </section>
 139
 140   <!-- XXX needs to be written
 141   <section id="RemovingWireshark"><title>Removing Wireshark</title>
 142     <para>
 143     </para>
 144   </section>
 145   -->
 146
 147   <section id="FileLocations"><title>File Locations</title>
 148     <para>
 149       Wireshark and TShark look in several different locations for
 150       preference files, plugins, SNMP MIBS, and RADIUS dictionaries.
 151       These locations vary from platform to platform.  You can use
 152       About->Folders to find the default locations on your system.
 153     </para>
 154   </section>
 155
 156   <section id="KnownProblems"><title>Known Problems</title>
 157
 158     <para>
 159       Wireshark may appear offscreen on multi-monitor Windows systems.
 160       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553">Bug
 161       553</ulink>)
 162     </para>
 163
 164     <para>
 165       Wireshark might make your system disassociate from a wireless network
 166       on OS X.
 167       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1315">Bug
 168       1315</ulink>)
 169     </para>
 170
 171     <para>
 172       Dumpcap might not quit if Wireshark or TShark crashes.
 173       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419">Bug
 174       1419</ulink>)
 175     </para>
 176
 177     <para>
 178       Wireshark is unable to decrypt WPA group keys.
 179       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1420">Bug
 180       1420</ulink>)
 181     </para>
 182
 183     <para>
 184       The BER dissector might infinitely loop.
 185       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516">Bug
 186       1516</ulink>)
 187     </para>
 188
 189     <para>
 190       Wireshark can't dynamically update the packet list. This means that host
 191       name resolutions above a certain response time threshold won't show up in
 192       the packet list.
 193       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1605">Bug
 194       1605</ulink>)
 195     </para>
 196
 197     <para>
 198       Capture filters aren't applied when capturing from named pipes.
 199       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814">Bug
 200       1814</ulink>)
 201     </para>
 202
 203     <para>
 204       Wireshark might freeze when reading from a pipe.
 205       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2082">Bug
 206       2082</ulink>)
 207     </para>
 208
 209     <para>
 210       Capturing from named pipes might be delayed on Windows.
 211       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2200">Bug
 212       2200</ulink>)
 213     </para>
 214
 215     <para>
 216       Filtering tshark captures with display filters (-R) no longer works.
 217       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234">Bug
 218       2234</ulink>)
 219     </para>
 220
 221   </section>
 222
 223   <section id="GettingHelp"><title>Getting Help</title>
 224     <para>
 225     Community support is available on the wireshark-users mailing list.
 226     Subscription information and archives for all of Wireshark's mailing
 227     lists can be found on <ulink url="http://www.wireshark.org/lists/">the
 228     web site</ulink>.
 229     </para>
 230     <para>
 231     Commercial support, training, and development services are available
 232     from <ulink url="http://www.cacetech.com/">CACE Technologies</ulink>.
 233     </para>
 234   </section>
 235
 236   <section id="FAQ"><title>Frequently Asked Questions</title>
 237     <para>
 238     A complete FAQ is available on the
 239     <ulink url="http://www.wireshark.org/faq.html">Wireshark web site</ulink>.
 240     </para>
 241   </section>
 242
 243 </article>