blob: 2d622af78199b3bc8ab3e363f5178c53069f50fb (
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
|
<?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 "1.3.4">
]>
<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 id="BugFixes"><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>
The NetFlow dissector could run off with your dog, crash your truck,
and write a country music song about the experience.
<!-- Fixed in r????? -->
<!-- (Bug <ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=????">????</ulink>) -->
</para>
<para>Versions affected: 0.99.5 to 1.0.8</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>
Wireshark could crash without warning.
</para></listitem>
</itemizedlist>
</para>
</section>
<section id="NewFeatures"><title>New and Updated Features</title>
<para>
The following features are new (or have been significantly updated)
since version 1.2:
<itemizedlist>
<listitem>
<para>
The packet list internals have been rewritten and are now more
efficient.
</para>
</listitem>
<listitem>
<para>
Python scripting support has been added.
</para>
</listitem>
<listitem>
<para>
Capturing from pipes on Windows has been improved.
</para>
</listitem>
<listitem>
<para>
Many memory leaks have been fixed.
</para>
</listitem>
<listitem>
<para>
Wireshark no longer supports Windows 2000. Please use
Wireshark 1.2 or 1.0 on those systems.
</para>
</listitem>
<listitem>
<para>
Packtets can now be ignored (excluded from dissection), similar to
the way they can be marked.
</para>
</listitem>
</itemizedlist>
</para>
</section>
<section id="NewProtocols"><title>New Protocol Support</title>
<para>
</para>
</section>
<section id="UpdatedProtocols"><title>Updated Protocol Support</title> <para>
</para>
</section>
<section id="NewCapture"><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
<ulink url="http://www.wireshark.org/download.html">http://www.wireshark.org/download.html</ulink>.
</para>
<section id="VendorPackages"><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>
Wireshark may appear offscreen on multi-monitor Windows systems.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553">Bug
553</ulink>)
</para>
<para>
Wireshark might make your system disassociate from a wireless network
on OS X.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1315">Bug
1315</ulink>)
</para>
<para>
Dumpcap might not quit if Wireshark or TShark crashes.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419">Bug
1419</ulink>)
</para>
<para>
Wireshark is unable to decrypt WPA group keys.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1420">Bug
1420</ulink>)
</para>
<para>
The BER dissector might infinitely loop.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516">Bug
1516</ulink>)
</para>
<para>
Wireshark can't dynamically update the packet list. This means that host
name resolutions above a certain response time threshold won't show up in
the packet list.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1605">Bug
1605</ulink>)
</para>
<para>
Capture filters aren't applied when capturing from named pipes.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814">Bug
1814</ulink>)
</para>
<para>
Wireshark might freeze when reading from a pipe.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2082">Bug
2082</ulink>)
</para>
<para>
Capturing from named pipes might be delayed on Windows.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2200">Bug
2200</ulink>)
</para>
<para>
Filtering tshark captures with display filters (-R) no longer works.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234">Bug
2234</ulink>)
</para>
<para>
The 64-bit Windows installer does not ship with the same libraries as the
32-bit installer.
(<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3610">Bug
3610</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>
|
