Wireshark-dev: [Wireshark-dev] Wireshark 2.0.9 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 14 Dec 2016 10:54:31 -0800
I'm proud to announce the release of Wireshark 2.0.9. __________________________________________________________________ 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 vulnerabilities have been fixed: * Arbitrary file deletion on Windows. ([1]Bug 13217) The following bugs have been fixed: * Saving all exported objects (SMB/SMB2) results in out of physical memory. ([2]Bug 11133) * Export HTTP Objects - Single file shows as multiple files in 2.0.2. ([3]Bug 12230) * Dicom list of tags in element of VR=AT not properly decoded. ([4]Bug 13077) * Malformed Packet: BGP Update (withdraw) message. ([5]Bug 13146) * GTP: "Create PDP Context response" message shows back-off timer as malformed when included in the response. ([6]Bug 13153) * ICMP dissector fails to properly detect timestamps. ([7]Bug 13161) * RLC misdissection. ([8]Bug 13162) * Text2pcap on windows produces corrupt output when writing the capture file to the standard output. ([9]Bug 13165) * TShark doesn't respect protocols.display_hidden_proto_items setting. ([10]Bug 13192) * RPC/RDMA dissector should exit when frame is not RPC-over-RDMA. ([11]Bug 13195) * Some RPC-over-RDMA frames are not recognized as RPC-over-RDMA. ([12]Bug 13196) * Wireshark shows "MS Video Source Request" in a RTCP packet as "Malformed". ([13]Bug 13212) New and Updated Features There are no new features in this release. New File Format Decoding Support There are no new file formats in this release. New Protocol Support There are no new protocols in this release. Updated Protocol Support BGP, BTLE, DICOM, GTP, ICMP, RPC over RDMA, RTCP, SDP, and SMB New and Updated Capture File Support There is no new or updated capture file support in this release. New and Updated Capture Interfaces support There are no new or updated capture interfaces supported in this release. __________________________________________________________________ Getting Wireshark Wireshark source code and installation packages are available from [14]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 [15]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. ([16]Bug 1419) The BER dissector might infinitely loop. ([17]Bug 1516) Capture filters aren't applied when capturing from named pipes. ([18]Bug 1814) Filtering tshark captures with read filters (-R) no longer works. ([19]Bug 2234) Application crash when changing real-time option. ([20]Bug 4035) Wireshark and TShark will display incorrect delta times in some cases. ([21]Bug 4985) Wireshark should let you work with multiple capture files. ([22]Bug 10488) Dell Backup and Recovery (DBAR) makes many Windows applications crash, including Wireshark. ([23]Bug 12036) __________________________________________________________________ Getting Help Community support is available on [24]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 [25]the web site. Official Wireshark training and certification are available from [26]Wireshark University. __________________________________________________________________ Frequently Asked Questions A complete FAQ is available on the [27]Wireshark web site. __________________________________________________________________ Last updated 2016-12-14 17:56:05 UTC References 1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13217 2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11133 3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12230 4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13077 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13146 6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13153 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13161 8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13162 9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13165 10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13192 11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13195 12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13196 13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13212 14. https://www.wireshark.org/download.html 15. https://www.wireshark.org/download.html#thirdparty 16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419 17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516 18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814 19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234 20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035 21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985 22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488 23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12036 24. https://ask.wireshark.org/ 25. https://www.wireshark.org/lists/ 26. http://www.wiresharktraining.com/ 27. https://www.wireshark.org/faq.html Digests wireshark-2.0.9.tar.bz2: 31154057 bytes SHA256(wireshark-2.0.9.tar.bz2)=aeff0122674a9551810e78b818b59f8a3a3e2055299117139136e7ca5ae23f2c RIPEMD160(wireshark-2.0.9.tar.bz2)=55bff5fc79411332d1856d9c2fb08ad3aa4bf2e1 SHA1(wireshark-2.0.9.tar.bz2)=63756e54b121222451f82651cf1d35c79b813d1b MD5(wireshark-2.0.9.tar.bz2)=632a5b2010b8f5e88bf1515131be67d5 Wireshark-win64-2.0.9.exe: 47761320 bytes SHA256(Wireshark-win64-2.0.9.exe)=cb83702378ca329a466b0be1c4410d8d3a5668188e174986024789234bb6e960 RIPEMD160(Wireshark-win64-2.0.9.exe)=f45935dbc361f8894249f1c2647cdc019e862d72 SHA1(Wireshark-win64-2.0.9.exe)=0a312095fac8f62e16c5fa983bba22dd596503dd MD5(Wireshark-win64-2.0.9.exe)=6d15dd6e4128dd5edd4373ba60bba05c Wireshark-win32-2.0.9.exe: 44130064 bytes SHA256(Wireshark-win32-2.0.9.exe)=c9bef1f71366096bb62f6ce65b50310ae9bba907d3c38acd998d5e0cfed974e6 RIPEMD160(Wireshark-win32-2.0.9.exe)=eba99cbb9acb2397758a01aea00dd7e539c33ff8 SHA1(Wireshark-win32-2.0.9.exe)=6eebcce800f30d2833190c0fbda67b7292c16815 MD5(Wireshark-win32-2.0.9.exe)=26bd9fc914772a7d759b59568e2c5963 WiresharkPortable_2.0.9.paf.exe: 43810016 bytes SHA256(WiresharkPortable_2.0.9.paf.exe)=9ab68f3386af8f953d3ac787aac7ce79fbac6a67ca81827de0e91619b8637ca8 RIPEMD160(WiresharkPortable_2.0.9.paf.exe)=9b8d4048754f4ba9bde5c48722bb3025e39c3f51 SHA1(WiresharkPortable_2.0.9.paf.exe)=1af6c65a96d9b75e967650cff4852660548846a6 MD5(WiresharkPortable_2.0.9.paf.exe)=2f925b932476c2cf5f554a2713a5f781 Wireshark 2.0.9 Intel 32.dmg: 32484735 bytes SHA256(Wireshark 2.0.9 Intel 32.dmg)=26f3e5b2b4d85ec0e63f4c56c503a67ab7e53362b6ad9dc39ee6d78159e5d547 RIPEMD160(Wireshark 2.0.9 Intel 32.dmg)=5d3108267e5b2a8784da1906af5cded6568c2d70 SHA1(Wireshark 2.0.9 Intel 32.dmg)=f3eb975e3878c27731c9a5f1486e1a8d5449fecf MD5(Wireshark 2.0.9 Intel 32.dmg)=04f66d9342841a195cd9c8954a1203d9 Wireshark 2.0.9 Intel 64.dmg: 31735308 bytes SHA256(Wireshark 2.0.9 Intel 64.dmg)=3876b00333cbbff9cf209b66c0cb2c8ed64c2e5ff9b749ca7e425dce00125dfa RIPEMD160(Wireshark 2.0.9 Intel 64.dmg)=55464b9cfb69e39caffc95489c9db298ded203a6 SHA1(Wireshark 2.0.9 Intel 64.dmg)=2b12761519be3cae7f7430977b5f2274533a184d MD5(Wireshark 2.0.9 Intel 64.dmg)=a80655357408836bfb4f3cede0faae27
Attachment:
signature.asc
Description: OpenPGP digital signature
- Prev by Date: [Wireshark-dev] Wireshark 2.2.3 is now available
- Next by Date: Re: [Wireshark-dev] how are the Radius dictionary files used?
- Previous by thread: [Wireshark-dev] Wireshark 2.2.3 is now available
- Next by thread: [Wireshark-dev] Redhat binaries
- Index(es):