Switch back to normal versioning. Bump the version to 1.3.3.
[obnox/wireshark/wip.git] / 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.3">
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         <listitem>
98           <para>
99             Many memory leaks have been fixed.
100           </para>
101         </listitem>
102
103       </itemizedlist>
104
105     </para>
106     </section>
107
108     <section id="NewProtocols"><title>New Protocol Support</title>
109     <para>
110
111     </para>
112     </section>
113
114     <section id="UpdatedProtocols"><title>Updated Protocol Support</title> <para>
115
116     </para>
117     </section>
118
119     <section id="NewCapture"><title>New and Updated Capture File Support</title>
120     <para>
121
122     </para>
123     </section>
124
125   </section>
126
127   <section id="GettingWireshark"><title>Getting Wireshark</title>
128     <para>
129       Wireshark source code and installation packages are available from
130       <ulink url="http://www.wireshark.org/download.html">http://www.wireshark.org/download.html</ulink>.
131     </para>
132
133     <section id="VendorPackages"><title>Vendor-supplied Packages</title>
134       <para>
135         Most Linux and Unix vendors supply their own Wireshark packages.
136         You can usually install or upgrade Wireshark using the package management
137         system specific to that platform.  A list of third-party packages
138         can be found on the
139         <ulink url="http://www.wireshark.org/download.html#otherplat">download page</ulink> on the Wireshark web site.
140       </para>
141     </section>
142
143   </section>
144
145   <!-- XXX needs to be written
146   <section id="RemovingWireshark"><title>Removing Wireshark</title>
147     <para>
148     </para>
149   </section>
150   -->
151
152   <section id="FileLocations"><title>File Locations</title>
153     <para>
154       Wireshark and TShark look in several different locations for
155       preference files, plugins, SNMP MIBS, and RADIUS dictionaries.
156       These locations vary from platform to platform.  You can use
157       About->Folders to find the default locations on your system.
158     </para>
159   </section>
160
161   <section id="KnownProblems"><title>Known Problems</title>
162
163     <para>
164       Wireshark may appear offscreen on multi-monitor Windows systems.
165       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553">Bug
166       553</ulink>)
167     </para>
168
169     <para>
170       Wireshark might make your system disassociate from a wireless network
171       on OS X.
172       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1315">Bug
173       1315</ulink>)
174     </para>
175
176     <para>
177       Dumpcap might not quit if Wireshark or TShark crashes.
178       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419">Bug
179       1419</ulink>)
180     </para>
181
182     <para>
183       Wireshark is unable to decrypt WPA group keys.
184       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1420">Bug
185       1420</ulink>)
186     </para>
187
188     <para>
189       The BER dissector might infinitely loop.
190       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516">Bug
191       1516</ulink>)
192     </para>
193
194     <para>
195       Wireshark can't dynamically update the packet list. This means that host
196       name resolutions above a certain response time threshold won't show up in
197       the packet list.
198       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1605">Bug
199       1605</ulink>)
200     </para>
201
202     <para>
203       Capture filters aren't applied when capturing from named pipes.
204       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814">Bug
205       1814</ulink>)
206     </para>
207
208     <para>
209       Wireshark might freeze when reading from a pipe.
210       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2082">Bug
211       2082</ulink>)
212     </para>
213
214     <para>
215       Capturing from named pipes might be delayed on Windows.
216       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2200">Bug
217       2200</ulink>)
218     </para>
219
220     <para>
221       Filtering tshark captures with display filters (-R) no longer works.
222       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234">Bug
223       2234</ulink>)
224     </para>
225
226     <para>
227       The 64-bit Windows installer does not ship with the same libraries as the
228       32-bit installer.
229       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3610">Bug
230       3610</ulink>)
231     </para>
232
233   </section>
234
235   <section id="GettingHelp"><title>Getting Help</title>
236     <para>
237     Community support is available on the wireshark-users mailing list.
238     Subscription information and archives for all of Wireshark's mailing
239     lists can be found on <ulink url="http://www.wireshark.org/lists/">the
240     web site</ulink>.
241     </para>
242     <para>
243     Commercial support, training, and development services are available
244     from <ulink url="http://www.cacetech.com/">CACE Technologies</ulink>.
245     </para>
246   </section>
247
248   <section id="FAQ"><title>Frequently Asked Questions</title>
249     <para>
250     A complete FAQ is available on the
251     <ulink url="http://www.wireshark.org/faq.html">Wireshark web site</ulink>.
252     </para>
253   </section>
254
255 </article>