-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.99.5.
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.3: * Qt port: + Several interface bugs have been fixed. + Translations have been updated. The following features are new (or have been significantly updated) since version 1.99.2: * Qt port: + Several bugs have been fixed. + You can now open a packet in a new window. + The Bluetooth ATT Server Attributes dialog has been added. + The Coloring Rules dialog has been added. + Many translations have been updated. Chinese, Italian and Polish translations are complete. + General user interface and usability improvements. + Automatic scrolling during capture now works. + The related packet indicator has been updated. The following features are new (or have been significantly updated) since version 1.99.1: * Qt port: + The welcome screen layout has been updated. + The Preferences dialog no longer crashes on Windows. + The packet list header menu has been added. + Statistics tree plugins are now supported. + The window icon is now displayed properly in the Windows taskbar. + A packet list an byte view selection bug has been fixed (Bug 10896) + The RTP Streams dialog has been added. + The Protocol Hierarchy Statistics dialog has been added. 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. + Support for HiDPI / Retina displays has been improved in the official packages. * DNS stats: + A new stats tree has been added to the Statistics menu. Now it is possible to collect stats such as qtype/qclass distribution, number of resource record per response section, and stats data (min, max, avg) for values such as query name length or DNS payload. * HPFEEDS stats: + A new stats tree has been added to the statistics menu. Now it is possible to collect stats per channel (messages count and payload size), and opcode distribution. * HTTP2 stats: + A new stats tree has been added to the statistics menu. Now it is possible to collect stats (type distribution). 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, BGP Monitoring Prototol (BMP), ceph, corosync/totemnet corosync cluster engine ( lowest levelencryption/decryption protocol), corosync/totemsrp corosync cluster engine ( totem single ring protocol), Couchbase, CP "Cooper" 2179, DJI UAV Drone Control Protocol, Dynamic Source Routing (RFC 4728), Elasticsearch, ETSI Card Application Toolkit - Transport Protocol, Generic Network Virtualization Encapsulation (Geneve), GVSP GigE Vision (TM) Streaming Protocol, HCrt, HiQnet, IPMI Trace, iSER, KNXnetIP, MACsec Key Agreement - EAPoL-MKA, MCPE (Minecraft Pocket Edition), OptoMMP, QNEX6 (QNET), RakNet games library, Remote Shared Virtual Disk - RSVD, Riemann, S7 Communication, Secure Socket Tunnel Protocol (SSTP), Shared Memory Communications - RDMA, Stateless Transport Tunneling, Video Services over IP (VSIP), and ZVT Kassenschnittstelle 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: * The emem framework (including all ep_ and se_ memory allocation routines) has been completely removed in favour of wmem which is now fully mature. * 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) 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) Wireshark should let you work with multiple capture files. (Bug 10488) __________________________________________________________________ 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 2015-03-19 16:38:42 UTC References 1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10896 2. https://www.wireshark.org/download.html 3. https://www.wireshark.org/download.html#thirdparty 4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516 6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234 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. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488 16. https://ask.wireshark.org/ 17. https://www.wireshark.org/lists/ 18. http://www.wiresharktraining.com/ 19. https://www.wireshark.org/faq.html Digests wireshark-1.99.5.tar.bz2: 29806267 bytes MD5(wireshark-1.99.5.tar.bz2)=e67475f4c94c28eb5d6979d5fcc3cb6f SHA1(wireshark-1.99.5.tar.bz2)=5dba845bc4f3cc5a7f3efcafe1b61297acee758e RIPEMD160(wireshark-1.99.5.tar.bz2)=ebec3c1dbe7bb017569abd2042423ca03118ba75 Wireshark-win32-1.99.5.exe: 35946872 bytes MD5(Wireshark-win32-1.99.5.exe)=88054f51d8108da7e1873fdee9b55ca6 SHA1(Wireshark-win32-1.99.5.exe)=e53eeb36057d1bdae8067be1e874f4d55669eccd RIPEMD160(Wireshark-win32-1.99.5.exe)=447986470ed5a381e0937faabe9f0d092dd1e7f3 Wireshark-win64-1.99.5.exe: 44248160 bytes MD5(Wireshark-win64-1.99.5.exe)=2b9891ed2060fc546554ed60601d36a5 SHA1(Wireshark-win64-1.99.5.exe)=492566d1b45f7fc1923326df234069d70d5d1e8f RIPEMD160(Wireshark-win64-1.99.5.exe)=d58a5efa994228d17cd6d89860e944d74a63d554 WiresharkPortable_1.99.5.paf.exe: 29624880 bytes MD5(WiresharkPortable_1.99.5.paf.exe)=06571cc868abb8af3bf09ea30153e956 SHA1(WiresharkPortable_1.99.5.paf.exe)=dedb4ac90b03339515faf3532abdd8a331c2e2ea RIPEMD160(WiresharkPortable_1.99.5.paf.exe)=0a51ca66129452e6828088a26b3a5a916e8259a2 Wireshark 1.99.5 Intel 64.dmg: 43359370 bytes MD5(Wireshark 1.99.5 Intel 64.dmg)=95d49c9a25c0b4e50a31d129809e17d4 SHA1(Wireshark 1.99.5 Intel 64.dmg)=a16e2b7510161f0e5a2bf5f005d739c82442c95d RIPEMD160(Wireshark 1.99.5 Intel 64.dmg)=4389902b23ab4f542803106835a82a554d613b7b Wireshark 1.99.5 Intel 32.dmg: 33541211 bytes MD5(Wireshark 1.99.5 Intel 32.dmg)=c119af38ed5b2efebd22eb7681eab950 SHA1(Wireshark 1.99.5 Intel 32.dmg)=71fb3b5a79c81154ca0d19c511fb111f1fda8254 RIPEMD160(Wireshark 1.99.5 Intel 32.dmg)=b8e8646b8f0d50f21afa53e44e44dc1c164f07ac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlULbeAACgkQpw8IXSHylJrE3wCg2Tz6tg4V50tKXImJBn0EeTZP WewAoKJJ191ccth+8NkTA9kKWgCrfcuu =Jcma -----END PGP SIGNATURE----- ___________________________________________________________________________ Sent via: Wireshark-announce mailing list <email@example.com> Archives: https://www.wireshark.org/lists/wireshark-announce Unsubscribe: https://wireshark.org/mailman/options/wireshark-announce mailto:wireshark-announce-requ...@wireshark.org?subject=unsubscribe