-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm proud to announce the release of Wireshark 1.11.0. This release marks a major change in the direction of the project. We're migrating our user interface library from GTK+ to Qt. The migration itself is incomplete but I'm excited about the features we have implemented so far and about what the future holds for Wireshark.
__________________________________________________________ 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 Bug Fixes The following bugs have been fixed: * "Follow TCP Stream" shows only the first HTTP req+res. (Bug 9044) * Files with pcap-ng Simple Packet Blocks can't be read. (Bug 9200) New and Updated Features The following features are new (or have been significantly updated) since version 1.10: * Wireshark now uses the Qt application framework. The new UI should provide a significantly better user experience, particularly on Mac OS X and Windows. * A more flexible, modular memory manger (wmem) has been added. It was available experimentally in 1.10 but is now mature and has mostly replaced the old API. * Expert info is now filterable and now requires a new API. * The Windows installer now uninstalls the previous version of Wireshark silently. You can still run the uninstaller manually beforehand if you wish to run it interactively. * The "Number" column shows related packets and protocol conversation spans (Qt only). * When manipulating packets with editcap using the -C <choplen> and/or -s <snaplen> options, it is now possible to also adjust the original frame length using the -L option. * You can now pass the -C <choplen> option to editcap multiple times, which allows you to chop bytes from the beginning of a packet as well as at the end of a packet in a single step. * You can now specify an optional offset to the -C option for editcap, which allows you to start chopping from that offset instead of from the absolute packet beginning or end. * "malformed" display filter has been renamed to "_ws.malformed". A handful of other filters have been given the "_ws." prefix to note they are Wireshark application specific filters and not dissector filters. New Protocol Support ASTERIX, SEL RTAC (Real Time Automation Controller) EIA-232 Serial-Line Dissection, and UDT Updated Protocol Support Too many protocols have been updated to list here. New and Updated Capture File Support Netscaler 2.6, and STANAG 4607 __________________________________________________________ Getting Wireshark Wireshark source code and installation packages are available from http://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. (ws-buglink: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) Summary pane selected frame highlighting not maintained. (Bug 4445) Wireshark and TShark will display incorrect delta times in some cases. (Bug 4985) The 64-bit Mac OS X installer doesn't support Mac OS X 10.9 (Bug 9242) __________________________________________________________ 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 2013-10-14 15:55:11 PDT References 1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044 2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9200 3. http://www.wireshark.org/download.html 4. http://www.wireshark.org/download.html#thirdparty 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419 6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234 8. https://wiki.wireshark.org/Development/Win64 9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9044 10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3528 11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035 12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4056 13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4357 14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4445 15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985 16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9242 17. http://ask.wireshark.org/ 18. http://www.wireshark.org/lists/ 19. http://www.wiresharktraining.com/ 20. http://www.wireshark.org/faq.html Digests wireshark-1.11.0.tar.bz2: 27492409 bytes MD5(wireshark-1.11.0.tar.bz2)=ffa7721cfd1c136718d9e08e09590c5e SHA1(wireshark-1.11.0.tar.bz2)=117e7d6ac65bcfda04d97dc4958dfe156d58c323 RIPEMD160(wireshark-1.11.0.tar.bz2)=e2e359ac029b878029e68392375ff6d4f10c0054 Wireshark-win32-1.11.0.exe: 27099024 bytes MD5(Wireshark-win32-1.11.0.exe)=b12fc6780b6ebfddfacf4f7c56b0b783 SHA1(Wireshark-win32-1.11.0.exe)=f8b82011149da1d56346b34cd490be431728c437 RIPEMD160(Wireshark-win32-1.11.0.exe)=63775782aeedf959a2b2bf69b18999805a9cab0c Wireshark-win64-1.11.0.exe: 33877768 bytes MD5(Wireshark-win64-1.11.0.exe)=dc6005b0c436a01fcbdd6086b8b44d45 SHA1(Wireshark-win64-1.11.0.exe)=deb50aeb111fac02ed7122e04e0576c34ca6a052 RIPEMD160(Wireshark-win64-1.11.0.exe)=25f003cf788bc7062ae5f6409bf2dad6f0dc4dcb WiresharkPortable-1.11.0.paf.exe: 28771296 bytes MD5(WiresharkPortable-1.11.0.paf.exe)=e25318ad4f4599ea9c3eab7c8cc0e8c6 SHA1(WiresharkPortable-1.11.0.paf.exe)=47a8b916528370940bd0098755a40570cf77cd78 RIPEMD160(WiresharkPortable-1.11.0.paf.exe)=c758a098281907c58552d50a60acba634d2b3c94 Wireshark 1.11.0 Intel 64.dmg: 34804824 bytes MD5(Wireshark 1.11.0 Intel 64.dmg)=7643ac20b5867e2d5d8ca15381370aae SHA1(Wireshark 1.11.0 Intel 64.dmg)=f2ed3e91a3fcb7af7e90ab7b72857db9c2a004b1 RIPEMD160(Wireshark 1.11.0 Intel 64.dmg)=a65838aa085b6b95d0432bbc155afe9262d3cc5e Wireshark 1.11.0 Intel 32.dmg: 20972818 bytes MD5(Wireshark 1.11.0 Intel 32.dmg)=bc243b244b32f24e07c33532d06e6d70 SHA1(Wireshark 1.11.0 Intel 32.dmg)=f0c7c2126968d2c37946c6910a4179518fb1678d RIPEMD160(Wireshark 1.11.0 Intel 32.dmg)=5ac3e13f5f6adfc4ed608249e72daac6aaa93fb7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJdqHUACgkQpw8IXSHylJplmgCgkMc0pPTrA8EF5GIgyk4Jq3OQ gdgAn2IuX4nHe9pnKsY8CmF4N+PkUkRW =r9oH -----END PGP SIGNATURE----- ___________________________________________________________________________ Sent via: Wireshark-announce mailing list <firstname.lastname@example.org> Archives: http://www.wireshark.org/lists/wireshark-announce Unsubscribe: https://wireshark.org/mailman/options/wireshark-announce mailto:wireshark-announce-requ...@wireshark.org?subject=unsubscribe