Emphasize that if you try to build on a system without GTK+ installed,
[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 "0.99.6">
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><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             Wireshark could crash when dissecting an HTTP chunked
41             response.
42             <!-- Fixed in r21034 -->
43             (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1394">1394</ulink>)
44           </para>
45           <para>Versions affected: 0.99.5</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         <listitem>
52           <para>
53             On some systems, Wireshark could crash while reading
54             iSeries capture files.
55             <!-- Fixed in r20990 -->
56             (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1415">1415</ulink>)
57           </para>
58           <para>Versions affected: 0.10.14 to 0.99.5</para>
59           <para>
60             <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
61           </para>
62         </listitem>
63
64         <listitem>
65           <para>
66             Wireshark could exhaust system memory while reading a malformed
67             DCP ETSI packet.
68             <!-- Fixed in r21007 -->
69             (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1264">1264</ulink>)
70           </para>
71           <para>Versions affected: 0.99.5</para>
72           <para>
73             <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
74           </para>
75         </listitem>
76
77         <listitem>
78           <para>
79             Defining a display filter macro with no arguments would make
80             Wireshark crash.
81             <!-- Fixed in r21664 -->
82             <!-- CID 232 -->
83           </para>
84           <para>Versions affected: 0.99.5</para>
85           <para>
86             <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
87           </para>
88         </listitem>
89
90         <listitem>
91           <para>
92             Wireshark could loop excessively while reading a malformed SSL
93             packet.
94             <!-- Fixed in r? -->
95             (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1582">1582</ulink>)
96           </para>
97           <para>Versions affected: ?</para>
98           <para>
99             <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
100           </para>
101         </listitem>
102
103       </itemizedlist>
104
105     </para>
106
107     <para>
108
109     The following bugs have been fixed:
110
111       <itemizedlist>
112
113         <listitem><para>
114           WEP decryption would only work for the first key specified.
115           disappear or become unusable.
116         </para></listitem>
117
118         <listitem><para>
119           Merging files in Wireshark now appends files properly.
120         </para></listitem>
121
122         <listitem><para>
123           Wireshark could hang while saving an RTP stream with bad timestamp
124           data.
125         </para></listitem>
126
127         <listitem><para>
128           You must now explicitly pass "--disable-wireshark" to the build
129           environment if you only want to build TShark; the configure
130           script will fail, rather than automatically building only
131           TShark, if it's run on a system that doesn't have GTK+ headers
132           and libraries installed.
133         </para></listitem>
134
135       </itemizedlist>
136     </para>
137
138     </section>
139
140     <section><title>New and Updated Features</title>
141     <para>
142       The following features are new (or have been significantly updated)
143       since the last release:
144
145       <!--
146       - HTTP object export
147       - Delta times
148       - Code cleanup
149       -->
150
151     </para>
152     </section>
153
154     <section><title>New Protocol Support</title>
155     <para>
156
157     </para>
158     </section>
159
160     <section><title>Updated Protocol Support</title> <para>
161
162     </para>
163     </section>
164
165     <section><title>New and Updated Capture File Support</title>
166     <para>
167
168     </para>
169     </section>
170
171   </section>
172
173   <section id="GettingWireshark"><title>Getting Wireshark</title>
174     <para>
175       Wireshark source code and installation packages are available from
176       the <ulink url="http://www.wireshark.org/download.html">download
177       page</ulink> on the main web site.
178     </para>
179
180     <section><title>Vendor-supplied Packages</title>
181       <para>
182         Most Linux and Unix vendors supply their own Wireshark packages.
183         You can usually install or upgrade Wireshark using the package management
184         system specific to that platform.  A list of third-party packages
185         can be found on the
186         <ulink url="http://www.wireshark.org/download.html#otherplat">download page</ulink> on the Wireshark web site.
187       </para>
188     </section>
189
190   </section>
191
192   <!-- XXX needs to be written
193   <section id="RemovingWireshark"><title>Removing Wireshark</title>
194     <para>
195     </para>
196   </section>
197   -->
198
199   <section id="FileLocations"><title>File Locations</title>
200     <para>
201       Wireshark and TShark look in several different locations for
202       preference files, plugins, SNMP MIBS, and RADIUS dictionaries.
203       These locations vary from platform to platform.  You can use
204       About->Folders to find the default locations on your system.
205     </para>
206   </section>
207
208   <section id="KnownProblems"><title>Known Problems</title>
209
210     <para>
211       The <guibutton>Filter</guibutton> button is nonfunctional in the
212       file dialogs under Windows.
213       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=942">Bug
214       942</ulink>)
215     </para>
216
217   </section>
218
219   <section id="GettingHelp"><title>Getting Help</title>
220     <para>
221     Community support is available on the wireshark-users mailing list.
222     Subscription information and archives for all of Wireshark's mailing
223     lists can be found on <ulink url="http://www.wireshark.org/lists/">the
224     web site</ulink>.
225     </para>
226     <para>
227     Commercial support, training, and development services are available
228     from <ulink url="http://www.cacetech.com/">CACE Technologies</ulink>.
229     </para>
230   </section>
231
232   <section id="FAQ"><title>Frequently Asked Questions</title>
233     <para>
234     A complete FAQ is available on the
235     <ulink url="http://www.wireshark.org/faq.html">Wireshark web site</ulink>.
236     </para>
237   </section>
238
239 </article>