Wireshark-dev: [Wireshark-dev] Wireshark 1.99.1 is now available
From: Gerald Combs <[email protected]>
Date: Wed, 10 Dec 2014 11:13:23 -0800
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.99.1. 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.99.0: * Qt port: + You can now show and hide toolbars and major widgets using the View menu. + You can now set the time display format and precision. + The byte view widget is much faster, particularly when selecting large reassembled packets. + The byte view is explorable. Hovering over it highlights the corresponding field and shows a description in the status bar. + An Italian translation has been added. + The Summary dialog has been updated and renamed to Capture File Properties. + The VoIP Calls and SIP Flows dialogs have been added. 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 (LISP) TCP Control Message, AllJoyn Reliable Datagram Protocol, Android ADB, Android Logcat text, ceph, corosync/totemnet, corosync/totemsrp, Couchbase, CP "Cooper" 2179, Dynamic Source Routing (RFC 4728), Elasticsearch, Generic Network Virtualization Encapsulation (Geneve), GVSP, HiQnet, IPMI Trace, iSER, KNXnetIP, MCPE (Minecraft Pocket Edition), OptoMMP, RakNet games library, Riemann, S7 Communication, Shared Memory Communications - RDMA, 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, Colasoft Capsa 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 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 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. (Bug 1419) The BER dissector might infinitely loop. (Bug 1516) Capture filters aren't applied when capturing from named pipes. (Bug 1814) Filtering tshark captures with read filters (-R) no longer works. (Bug 2234) The 64-bit Windows installer does not support Kerberos decryption. (Win64 development page) Resolving (Bug 9044) reopens (Bug 3528) so that Wireshark no longer automatically decodes gzip data when following a TCP stream. Application crash when changing real-time option. (Bug 4035) Hex pane display issue after startup. (Bug 4056) Packet list rows are oversized. (Bug 4357) Wireshark and TShark will display incorrect delta times in some cases. (Bug 4985) The 64-bit version of Wireshark will leak memory on Windows when the display depth is set to 16 bits (Bug 9914) __________________________________________________________________ Getting Help Community support is available on 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 the web site. Official Wireshark training and certification are available from Wireshark University. __________________________________________________________________ Frequently Asked Questions A complete FAQ is available on the Wireshark web site. __________________________________________________________________ Last updated 2014-12-10 17:36: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.1.tar.bz2: 29981374 bytes MD5(wireshark-1.99.1.tar.bz2)=ecba656afd5cf666488828a545144599 SHA1(wireshark-1.99.1.tar.bz2)=5ea32f83709a90fd5fdf5d331992e46a42ec27aa RIPEMD160(wireshark-1.99.1.tar.bz2)=87fe7504e02d9c91bf07547114f829cdf71f8e87 Wireshark-win32-1.99.1.exe: 37467288 bytes MD5(Wireshark-win32-1.99.1.exe)=62decf3e766456fccc9ff56ff532c2d8 SHA1(Wireshark-win32-1.99.1.exe)=9a604894b5041c328ded549c3ff36f03e9f7b9b4 RIPEMD160(Wireshark-win32-1.99.1.exe)=47858f9a6b05eaf3e467f0003fbfd03452ba6c31 Wireshark-win64-1.99.1.exe: 46353328 bytes MD5(Wireshark-win64-1.99.1.exe)=6e06ed9f18feb2cbd3845022e94fc766 SHA1(Wireshark-win64-1.99.1.exe)=4c86a8c02285998bae2bdede37a440fdef61ee25 RIPEMD160(Wireshark-win64-1.99.1.exe)=30f194e819dc6b7f178525f68a59dacc05f6bc86 WiresharkPortable_1.99.1.paf.exe: 28899952 bytes MD5(WiresharkPortable_1.99.1.paf.exe)=6407bf463535ebd7184867672479d5db SHA1(WiresharkPortable_1.99.1.paf.exe)=2f3bba965f78ef990b059747b0972d4d4f8bf56c RIPEMD160(WiresharkPortable_1.99.1.paf.exe)=c6993015ec092418937a1fd46f6af74573422ff5 Wireshark 1.99.1 Intel 32.dmg: 33082865 bytes MD5(Wireshark 1.99.1 Intel 32.dmg)=99527517eaa5b47ac1d57b3952886db7 SHA1(Wireshark 1.99.1 Intel 32.dmg)=06f60eab426bce7bae26fc1c08c298acbc93f978 RIPEMD160(Wireshark 1.99.1 Intel 32.dmg)=2001090f8715c3288169d233f86b55464e742f7d Wireshark 1.99.1 Intel 64.dmg: 42809185 bytes MD5(Wireshark 1.99.1 Intel 64.dmg)=1968632518f70cecac31834433e916d8 SHA1(Wireshark 1.99.1 Intel 64.dmg)=8fd550713cd0b93930c37430302c76484d196b76 RIPEMD160(Wireshark 1.99.1 Intel 64.dmg)=a6d5ad4d31b160cd8b6c1ec413871c87e78d4ab4 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlSIm1MACgkQpw8IXSHylJpN1wCg2Dn0QkZDNMDxikSBFDmmkX++ ZHkAn2TegysbOKS9bpZKNWi/LygjxsYx =Y6Sb -----END PGP SIGNATURE-----
- Prev by Date: Re: [Wireshark-dev] [Wireshark-commits] master 3147087: Fix ranlib "has no symbols" errors in the codecs directory.
- Next by Date: [Wireshark-dev] Getting involved with Wireshark (was: Re: What Wireshark base version to use for customization)
- Previous by thread: Re: [Wireshark-dev] [!!Mass Mail]Re: What Wireshark base version to use for customization
- Next by thread: [Wireshark-dev] Tiny Remote Wireshark Sensor goes wireless