aboutsummaryrefslogtreecommitdiffstats
path: root/docbook/release-notes.xml
blob: 83a987aec22cf4a66e70514989cc9b3151587936 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
<?xml version="1.0"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [

<!-- $Id$ -->

<!--
DOCUMENT SECTION
-Use this section to encode all document information
-->

<!--
Wireshark Info
-->
  <!ENTITY WiresharkCurrentVersion "0.99.6">

]>

<article>
  <title>Wireshark &WiresharkCurrentVersion; Release Notes</title>

  <section id="WhatIs"><title>What is Wireshark?</title>
    <para>
      Wireshark is the world's most popular network protocol analyzer.  It
      is used for troubleshooting, analysis, development, and education.
    </para>
  </section>

  <section id="WhatsNew"><title>What's New</title>
    <section><title>Bug Fixes</title>
    <para>

      The following vulnerabilities have been fixed.  See the
      <ulink url="http://www.wireshark.org/security/wnpa-sec-2007-02.html">security advisory</ulink> for details and a workaround.

      <itemizedlist>

        <listitem>
          <para>
            Wireshark could crash when dissecting an HTTP chunked
            response.
            <!-- Fixed in r21034 -->
            (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1394">1394</ulink>)
          </para>
          <para>Versions affected: 0.99.5</para>
          <para>
            <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
          </para>
        </listitem>

        <listitem>
          <para>
            On some systems, Wireshark could crash while reading
            iSeries capture files.
            <!-- Fixed in r20990 -->
            (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1415">1415</ulink>)
          </para>
          <para>Versions affected: 0.10.14 to 0.99.5</para>
          <para>
            <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
          </para>
        </listitem>

        <listitem>
          <para>
            Wireshark could exhaust system memory while reading a malformed
            DCP ETSI packet.
            <!-- Fixed in r21007 -->
            (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1264">1264</ulink>)
          </para>
          <para>Versions affected: 0.99.5</para>
          <para>
            <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
          </para>
        </listitem>

        <listitem>
          <para>
            Wireshark could loop excessively while reading a malformed SSL
            packet.
            <!-- Fixed in r? -->
            (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1582">1582</ulink>)
          </para>
          <para>Versions affected: ?</para>
          <para>
            <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
          </para>
        </listitem>

        <listitem>
          <para>
            The DHCP/BOOTP dissector was susceptible to an off-by-one error.
            <!-- Fixed in r21947 -->
            (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1416">1416</ulink>)
          </para>
          <para>Versions affected: ?</para>
          <para>
            <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
          </para>
        </listitem>

        <listitem>
          <para>
            Wireshark could loop excessively while reading a malformed MMS
            packet.
            <!-- Fixed in r21392 -->
            (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1382">1382</ulink>)
          </para>
          <para>Versions affected: ?</para>
          <para>
            <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
          </para>
        </listitem>

      </itemizedlist>

    </para>

    <para>

    The following bugs have been fixed:

      <itemizedlist>

        <listitem><para>
          WEP decryption would only work for the first key specified.
          disappear or become unusable.  WEP and WPA decryption didn't work
          for QoS frames.  WPA decryption failed if EAPOL handshake packets
          contained extra data.  Wireshark failed to parse colon-separated
          WEP keys.
        </para></listitem>

        <listitem><para>
          Merging files in Wireshark now appends files properly.
        </para></listitem>

        <listitem><para>
          Wireshark could hang while saving an RTP stream with bad timestamp
          data.
        </para></listitem>

        <listitem><para>
          You must now explicitly pass "--disable-wireshark" to the build
          environment if you only want to build TShark; the configure
          script will fail, rather than automatically building only
          TShark, if it's run on a system that doesn't have GTK+ headers
          and libraries installed.
        </para></listitem>

        <listitem><para>
	  Capture from named pipes (via "-i
	  \\&lt;server&gt;\pipe\&lt;pipename&gt;") now works under
	  Windows.
        </para></listitem>

        <listitem><para>
          The <screen>frame.time_delta</screen> display filter now works as
          expected, matching the delta time between the current and previous
          <emphasis>captured</emphasis> packet.  A new filter,
          <screen>frame.time_delta_displayed</screen>,
          matches the delta time between the current and previous
          <emphasis>displayed</emphasis> frame.
        </para></listitem>

      </itemizedlist>
    </para>

    </section>

    <section><title>New and Updated Features</title>
    <para>
      The following features are new (or have been significantly updated)
      since the last release:

      <itemizedlist>

        <listitem><para>
          You no longer have to restart Wireshark after changing column
          preferences.
        </para></listitem>

        <listitem><para>
          You can now export HTTP objects via File&rarr;Export&rarr;Objects&rarr;HTML.
        </para></listitem>

        <listitem><para>
          Wireshark now supports display filter macros
        </para></listitem>

        <listitem><para>
          <ulink url="http://www.wireshark.org/docs/wsug_html_chunked/ChDisplayFilterMacrosSection.html">Display
          filter macros</ulink> are now supported.
        </para></listitem>

        <listitem><para>
          You can now match upper- and lower-case text with the <screen>contains</screen> operator, e.g. <programlisting>upper(http.request.method) contains "GET"</programlisting>.
        </para></listitem>

        <listitem><para>
          A great deal of code has been cleaned up, including fixing many
          compiler errors.
        </para></listitem>

      </itemizedlist>
    </para>
    </section>

    <section><title>New Protocol Support</title>
    <para>

    </para>
    </section>

    <section><title>Updated Protocol Support</title> <para>

    </para>
    </section>

    <section><title>New and Updated Capture File Support</title>
    <para>

    </para>
    </section>

  </section>

  <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.
    </para>

    <section><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
	system specific to that platform.  A list of third-party packages
	can be found on the
	<ulink url="http://www.wireshark.org/download.html#otherplat">download page</ulink> on the Wireshark web site.
      </para>
    </section>

  </section>

  <!-- XXX needs to be written
  <section id="RemovingWireshark"><title>Removing Wireshark</title>
    <para>
    </para>
  </section>
  -->

  <section id="FileLocations"><title>File Locations</title>
    <para>
      Wireshark and TShark look in several different locations for
      preference files, plugins, SNMP MIBS, and RADIUS dictionaries.
      These locations vary from platform to platform.  You can use
      About->Folders to find the default locations on your system.
    </para>
  </section>

  <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>)
    </para>

  </section>

  <section id="GettingHelp"><title>Getting Help</title>
    <para>
    Community support is available on the wireshark-users mailing list.
    Subscription information and archives for all of Wireshark's mailing
    lists can be found on <ulink url="http://www.wireshark.org/lists/">the
    web site</ulink>.
    </para>
    <para>
    Commercial support, training, and development services are available
    from <ulink url="http://www.cacetech.com/">CACE Technologies</ulink>.
    </para>
  </section>

  <section id="FAQ"><title>Frequently Asked Questions</title>
    <para>
    A complete FAQ is available on the
    <ulink url="http://www.wireshark.org/faq.html">Wireshark web site</ulink>.
    </para>
  </section>

</article>