Wireshark-dev: [Wireshark-dev] Wireshark 1.99.0 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Tue, 07 Oct 2014 12:35:45 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm proud to announce the release of Wireshark 1.99.0.
This is an experimental release intended to test new features
for Wireshark 2.0.
__________________________________________________________
What is Wireshark?
Wireshark is the world's most popular network protocol
analyzer. It is used for troubleshooting, analysis, development
and education.
__________________________________________________________
What's New
New and Updated Features
The following features are new (or have been significantly
updated) since version 1.12.0:
* The I/O Graph in the Gtk+ UI now supports an unlimited
number of data points (up from 100k).
* TShark now resets its state when changing files in
ring-buffer mode.
* Expert Info severities can now be configured.
* Wireshark now supports external capture interfaces.
External capture interfaces can be anything from a
tcpdump-over-ssh pipe to a program that captures from
proprietary or non-standard hardware. This functionality is
not available in the Qt UI yet.
* Qt port:
+ The Qt UI is now the default (program name is
wireshark).
+ A Polish translation has been added.
+ The Interfaces dialog has been added.
+ The interface list is now updated when interfaces
appear or disappear.
+ The Conversations and Endpoints dialogs have been
added.
+ A Japanese translation has been added.
+ It is now possible to manage remote capture
interfaces.
+ Windows: taskbar progress support has been added.
+ Most toolbar actions are in place and work.
+ More command line options are now supported
New Protocol Support
ceph, corosync/totemnet, corosync/totemsrp, CP "Cooper" 2179,
Dynamic Source Routing (RFC 4728), Generic Network
Virtualization Encapsulation (Geneve), IPMI Trace, iSER,
KNXnetIP, OptoMMP, S7 Communication, and Stateless Transport
Tunneling
Updated Protocol Support
Too many protocols have been updated to list here.
New and Updated Capture File Support
Android logcat text files, and Wireshark now supports
nanosecond timestamp resolution in PCAP-NG files.
Major API Changes
The libwireshark API has undergone some major changes:
* Many of the ep_ and se_ memory allocation routines have
been removed.
* The (long-since-broken) Python bindings support has been
removed. If you want to write dissectors in something other
than C, use Lua.
__________________________________________________________
Getting Wireshark
Wireshark source code and installation packages are available
from [1]https://www.wireshark.org/download.html.
Vendor-supplied Packages
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 [2]download page on
the Wireshark web site.
__________________________________________________________
File Locations
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.
__________________________________________________________
Known Problems
Dumpcap might not quit if Wireshark or TShark crashes. ([3]Bug
1419)
The BER dissector might infinitely loop. ([4]Bug 1516)
Capture filters aren't applied when capturing from named pipes.
([5]Bug 1814)
Filtering tshark captures with read filters (-R) no longer
works. ([6]Bug 2234)
The 64-bit Windows installer does not support Kerberos
decryption. ([7]Win64 development page)
Resolving ([8]Bug 9044) reopens ([9]Bug 3528) so that Wireshark
no longer automatically decodes gzip data when following a TCP
stream.
Application crash when changing real-time option. ([10]Bug
4035)
Hex pane display issue after startup. ([11]Bug 4056)
Packet list rows are oversized. ([12]Bug 4357)
Wireshark and TShark will display incorrect delta times in some
cases. ([13]Bug 4985)
The 64-bit version of Wireshark will leak memory on Windows
when the display depth is set to 16 bits ([14]Bug 9914)
__________________________________________________________
Getting Help
Community support is available on [15]Wireshark's Q&A site and
on the wireshark-users mailing list. Subscription information
and archives for all of Wireshark's mailing lists can be found
on [16]the web site.
Official Wireshark training and certification are available
from [17]Wireshark University.
__________________________________________________________
Frequently Asked Questions
A complete FAQ is available on the [18]Wireshark web site.
__________________________________________________________
Last updated 2014-10-07 16:16:57 UTC
References
1. https://www.wireshark.org/download.html
2. https://www.wireshark.org/download.html#thirdparty
3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
7. http://wiki.wireshark.org/Development/Win64
8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044
9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3528
10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056
12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357
13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9914
15. http://ask.wireshark.org/
16. https://www.wireshark.org/lists/
17. http://www.wiresharktraining.com/
18. https://www.wireshark.org/faq.html
Digests
wireshark-1.99.0.tar.bz2: 29782811 bytes
MD5(wireshark-1.99.0.tar.bz2)=7f605126da1599c28a0d557026d3576b
SHA1(wireshark-1.99.0.tar.bz2)=2e5cf3209104b98251350b3a5e52401866916aec
RIPEMD160(wireshark-1.99.0.tar.bz2)=c5efda1c2d0718fb9184f145d3763b77eeec8e40
Wireshark-win32-1.99.0.exe: 37235736 bytes
MD5(Wireshark-win32-1.99.0.exe)=9ba3f8307f1832f01ce761dd38dce26d
SHA1(Wireshark-win32-1.99.0.exe)=a677489d52be958dfa1ebffd419c0388d932137a
RIPEMD160(Wireshark-win32-1.99.0.exe)=e0cd8acd36df2fc4efd97fe36a76defadfb80a36
Wireshark-win64-1.99.0.exe: 45750624 bytes
MD5(Wireshark-win64-1.99.0.exe)=628c54467c50f289bed2983e7d372859
SHA1(Wireshark-win64-1.99.0.exe)=eac977130d83914f7e3cd61c9fcb58bb00d82e73
RIPEMD160(Wireshark-win64-1.99.0.exe)=03b12c26a1e59668da62890cbecef9a21ade2221
WiresharkPortable_1.99.0.paf.exe: 28592232 bytes
MD5(WiresharkPortable_1.99.0.paf.exe)=cef7d54730ada3ac46c4b35566c347a1
SHA1(WiresharkPortable_1.99.0.paf.exe)=5a14f214320fc0e86a419ca6446bc5aa557d363c
RIPEMD160(WiresharkPortable_1.99.0.paf.exe)=fcd157e61c6393da85c8927a9999d88ad8280e89
Wireshark 1.99.0 Intel 32.dmg: 32787345 bytes
MD5(Wireshark 1.99.0 Intel 32.dmg)=8438756fb34e17e10a3d8304ad175999
SHA1(Wireshark 1.99.0 Intel
32.dmg)=1ef2feb39515358e86e2a233c71f028b5ef3d3b2
RIPEMD160(Wireshark 1.99.0 Intel
32.dmg)=cc2db381f79e6d7cb211f0b08b1fea556ae10999
Wireshark 1.99.0 Intel 64.dmg: 39264608 bytes
MD5(Wireshark 1.99.0 Intel 64.dmg)=2b1dacd0891187bba2403a8011bf4137
SHA1(Wireshark 1.99.0 Intel
64.dmg)=432ac637a33d95c930edcb5e4444745b5e14b8fd
RIPEMD160(Wireshark 1.99.0 Intel
64.dmg)=a88aa1f641f37efde4e33c10174980b5152e3a53
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (Darwin)
iEYEARECAAYFAlQ0QJEACgkQpw8IXSHylJpbTACglP7+vTpwh6suFXF0egcj/ohd
iLwAoJp3wX/sfodrDp/QWosG/Qfee2Bc
=OYgT
-----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-dev] Conflicts: field in commit messages
- Next by Date: Re: [Wireshark-dev] FW: [Wireshark-commits] master 5330875: GTK+: Revert back to 2.24.14-1.1 on Win64.
- Previous by thread: Re: [Wireshark-dev] Change in wireshark[master]: Overhaul the filterability of packet-ansi_683.c
- Next by thread: Re: [Wireshark-dev] FW: [Wireshark-commits] master 5330875: GTK+: Revert back to 2.24.14-1.1 on Win64.
- Index(es):