2 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
9 -Use this section to encode all document information
15 <!ENTITY WiresharkCurrentVersion "1.3.3">
20 <title>Wireshark &WiresharkCurrentVersion; Release Notes</title>
22 <section id="WhatIs"><title>What is Wireshark?</title>
24 Wireshark is the world's most popular network protocol analyzer. It
25 is used for troubleshooting, analysis, development, and education.
29 <section id="WhatsNew"><title>What's New</title>
30 <section id="BugFixes"><title>Bug Fixes</title>
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.
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>) -->
45 <para>Versions affected: 0.99.5 to 1.0.8</para>
47 <!-- <ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-????">CVE-2007-????</ulink> -->
57 The following bugs have been fixed:
62 Wireshark could crash without warning.
71 <section id="NewFeatures"><title>New and Updated Features</title>
73 The following features are new (or have been significantly updated)
80 The packet list internals have been rewritten and are now more
87 Python scripting support has been added.
93 Capturing from pipes on Windows has been improved.
99 Many memory leaks have been fixed.
105 Wireshark no longer supports Windows 2000. Please use Wireshark 1.2 or 1.0 on
115 <section id="NewProtocols"><title>New Protocol Support</title>
121 <section id="UpdatedProtocols"><title>Updated Protocol Support</title> <para>
126 <section id="NewCapture"><title>New and Updated Capture File Support</title>
134 <section id="GettingWireshark"><title>Getting Wireshark</title>
136 Wireshark source code and installation packages are available from
137 <ulink url="http://www.wireshark.org/download.html">http://www.wireshark.org/download.html</ulink>.
140 <section id="VendorPackages"><title>Vendor-supplied Packages</title>
142 Most Linux and Unix vendors supply their own Wireshark packages.
143 You can usually install or upgrade Wireshark using the package management
144 system specific to that platform. A list of third-party packages
146 <ulink url="http://www.wireshark.org/download.html#otherplat">download page</ulink> on the Wireshark web site.
152 <!-- XXX needs to be written
153 <section id="RemovingWireshark"><title>Removing Wireshark</title>
159 <section id="FileLocations"><title>File Locations</title>
161 Wireshark and TShark look in several different locations for
162 preference files, plugins, SNMP MIBS, and RADIUS dictionaries.
163 These locations vary from platform to platform. You can use
164 About->Folders to find the default locations on your system.
168 <section id="KnownProblems"><title>Known Problems</title>
171 Wireshark may appear offscreen on multi-monitor Windows systems.
172 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553">Bug
177 Wireshark might make your system disassociate from a wireless network
179 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1315">Bug
184 Dumpcap might not quit if Wireshark or TShark crashes.
185 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419">Bug
190 Wireshark is unable to decrypt WPA group keys.
191 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1420">Bug
196 The BER dissector might infinitely loop.
197 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516">Bug
202 Wireshark can't dynamically update the packet list. This means that host
203 name resolutions above a certain response time threshold won't show up in
205 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1605">Bug
210 Capture filters aren't applied when capturing from named pipes.
211 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814">Bug
216 Wireshark might freeze when reading from a pipe.
217 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2082">Bug
222 Capturing from named pipes might be delayed on Windows.
223 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2200">Bug
228 Filtering tshark captures with display filters (-R) no longer works.
229 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234">Bug
234 The 64-bit Windows installer does not ship with the same libraries as the
236 (<ulink url="http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3610">Bug
242 <section id="GettingHelp"><title>Getting Help</title>
244 Community support is available on the wireshark-users mailing list.
245 Subscription information and archives for all of Wireshark's mailing
246 lists can be found on <ulink url="http://www.wireshark.org/lists/">the
250 Commercial support, training, and development services are available
251 from <ulink url="http://www.cacetech.com/">CACE Technologies</ulink>.
255 <section id="FAQ"><title>Frequently Asked Questions</title>
257 A complete FAQ is available on the
258 <ulink url="http://www.wireshark.org/faq.html">Wireshark web site</ulink>.