gtk_label_set -> gtk_label_set_text
[metze/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.0.99">
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 X.509sat dissector could crash.
41             <!-- Fixed in r24543 -->
42             <!-- (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2329">2329</ulink>) -->
43           </para>
44           <para>Versions affected: 0.99.5 to 0.99.8</para>
45           <para>
46             <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
47           </para>
48         </listitem>
49
50         <listitem>
51           <para>
52             The Roofnet dissector could crash on Windows, Solaris, and
53             possibly other platforms.
54             <!-- Fixed in r24555 -->
55             <!-- (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2331">2331</ulink>) -->
56           </para>
57           <para>Versions affected: 0.99.5 to 0.99.8</para>
58           <para>
59             <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
60           </para>
61         </listitem>
62
63       </itemizedlist>
64
65     </para>
66
67     <para>
68
69     The following bugs have been fixed:
70
71       <itemizedlist>
72
73         <listitem><para>
74             Wireshark could crash without warning.
75         </para></listitem>
76
77       </itemizedlist>
78
79     </para>
80
81     </section>
82
83     <section id="NewFeatures"><title>New and Updated Features</title>
84     <para>
85       The following features are new (or have been significantly updated)
86       since the last release:
87
88       <itemizedlist>
89
90         <listitem>
91           <para>
92             Packet loss magically fixes itself.
93           </para>
94         </listitem>
95
96       </itemizedlist>
97
98     </para>
99     </section>
100
101     <section id="NewProtocols"><title>New Protocol Support</title>
102     <para>
103
104     </para>
105     </section>
106
107     <section id="UpdatedProtocols"><title>Updated Protocol Support</title> <para>
108
109     </para>
110     </section>
111
112     <section id="NewCapture"><title>New and Updated Capture File Support</title>
113     <para>
114
115     </para>
116     </section>
117
118   </section>
119
120   <section id="GettingWireshark"><title>Getting Wireshark</title>
121     <para>
122       Wireshark source code and installation packages are available from
123       the <ulink url="http://www.wireshark.org/download.html">download
124       page</ulink> on the main web site.
125     </para>
126
127     <section id="VendorPackages"><title>Vendor-supplied Packages</title>
128       <para>
129         Most Linux and Unix vendors supply their own Wireshark packages.
130         You can usually install or upgrade Wireshark using the package management
131         system specific to that platform.  A list of third-party packages
132         can be found on the
133         <ulink url="http://www.wireshark.org/download.html#otherplat">download page</ulink> on the Wireshark web site.
134       </para>
135     </section>
136
137   </section>
138
139   <!-- XXX needs to be written
140   <section id="RemovingWireshark"><title>Removing Wireshark</title>
141     <para>
142     </para>
143   </section>
144   -->
145
146   <section id="FileLocations"><title>File Locations</title>
147     <para>
148       Wireshark and TShark look in several different locations for
149       preference files, plugins, SNMP MIBS, and RADIUS dictionaries.
150       These locations vary from platform to platform.  You can use
151       About->Folders to find the default locations on your system.
152     </para>
153   </section>
154
155   <section id="KnownProblems"><title>Known Problems</title>
156
157     <para>
158       Wireshark may appear offscreen on multi-monitor Windows systems.
159       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553">Bug
160       553</ulink>)
161     </para>
162
163     <para>
164       Wireshark might make your system disassociate from a wireless network
165       on OS X.
166       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1315">Bug
167       1315</ulink>)
168     </para>
169
170     <para>
171       Dumpcap might not quit if Wireshark or TShark crashes.
172       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419">Bug
173       1419</ulink>)
174     </para>
175
176     <para>
177       Wireshark is unable to decrypt WPA group keys.
178       (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1420">Bug
179       1420</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   </section>
227
228   <section id="GettingHelp"><title>Getting Help</title>
229     <para>
230     Community support is available on the wireshark-users mailing list.
231     Subscription information and archives for all of Wireshark's mailing
232     lists can be found on <ulink url="http://www.wireshark.org/lists/">the
233     web site</ulink>.
234     </para>
235     <para>
236     Commercial support, training, and development services are available
237     from <ulink url="http://www.cacetech.com/">CACE Technologies</ulink>.
238     </para>
239   </section>
240
241   <section id="FAQ"><title>Frequently Asked Questions</title>
242     <para>
243     A complete FAQ is available on the
244     <ulink url="http://www.wireshark.org/faq.html">Wireshark web site</ulink>.
245     </para>
246   </section>
247
248 </article>