Wireshark-dev: [Wireshark-dev] Wireshark 3.0.5 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Fri, 20 Sep 2019 12:13:32 -0700
I'm proud to announce the release of Wireshark 3.0.5. 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 The Windows installers now ship with Qt 5.12.5. They previously shipped with Qt 5.12.4. If you have Npcap 0.994 or 0.995 installed, your system might crash when upgrading. We recommend that you uninstall these versions manually prior to installing Wireshark. See Npcap bugs 1591[1] and 1675[2] for more details. You can uninstall either version manually by doing the following: 1. Open a command or PowerShell prompt as Administrator and run `sc.exe config npcap start=disabled`. 2. Run `sc.exe config npf start=disabled`. This will fail if WinPcap compatibility mode isn’t enabled, but is otherwise harmless. 3. Reboot (optional). 4. Open “Programs and Features” in the Control Panel or “Apps & features” in Settings and uninstall Npcap. 5. Open “Device Manager” (devmgmt.msc) in the Control Panel and expand the “Network adapters” section. Uninstall each “Npcap Loopback Adapter” that you find. Bug Fixes The following vulnerabilities have been fixed: The following bugs have been fixed: • Qt interface crashes on a profile with packet list only. Bug 16048[3]. • Wireshark 3.0.4 does not start on macOS 10.13 after an upgrade from 3.0.3. Bug 16050[4]. • NET-SNMP EngineID Length handling Warning. Bug 16051[5]. • Upgrade from Wireshark 3.0.2/3.0.3 to 3.0.4/later is confusing and may not complete properly. Bug 16052[6]. • Crash SIGSEGV when decrypting IEEE 802.11 EAP re-authentications. Bug 16058[7]. New and Updated Features There are no new features in this release. New Protocol Support There are no new protocols in this release. Updated Protocol Support 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 is no new or updated capture file support in this release. Getting Wireshark Wireshark source code and installation packages are available from https://www.wireshark.org/download.html[8]. 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[9] 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. Getting Help The User’s Guide, manual pages and various other documentation can be found at https://www.wireshark.org/docs/[10] Community support is available on Wireshark’s Q&A site[11] 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[12]. Bugs and feature requests can be reported on the bug tracker[13]. Official Wireshark training and certification are available from Wireshark University[14]. Frequently Asked Questions A complete FAQ is available on the Wireshark web site[15]. Last updated 2019-09-20 18:17:15 UTC References 1. https://github.com/nmap/nmap/issues/1591 2. https://github.com/nmap/nmap/issues/1675 3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16048 4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16050 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16051 6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16052 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16058 8. https://www.wireshark.org/download.html 9. https://www.wireshark.org/download.html#thirdparty 10. https://www.wireshark.org/docs/ 11. https://ask.wireshark.org/ 12. https://www.wireshark.org/lists/ 13. https://bugs.wireshark.org/ 14. http://www.wiresharktraining.com/ 15. https://www.wireshark.org/faq.html Digests wireshark-3.0.5.tar.xz: 30929864 bytes SHA256(wireshark-3.0.5.tar.xz)=c551fce475c49cea317ccbf9d22404bc827dde9cee0ccdf6648bfed3ecd9f820 RIPEMD160(wireshark-3.0.5.tar.xz)=f4be43f526ae5ef4c42fc294a37418e360a565d4 SHA1(wireshark-3.0.5.tar.xz)=82883e96ee247d3fcacb0cafa0bed9112824ee3a Wireshark-win32-3.0.5.exe: 54066936 bytes SHA256(Wireshark-win32-3.0.5.exe)=3a08dc164a84835a6ad5b7c0a0c1ae58cc7ce4d13ab66a81e15e8ee3f079a94c RIPEMD160(Wireshark-win32-3.0.5.exe)=3ac04280cfed3554b91ee40ad0fc40229cc4da6d SHA1(Wireshark-win32-3.0.5.exe)=cc9e0afcfd83e4f64be1e3191987b813b7977a31 Wireshark-win64-3.0.5.exe: 59271840 bytes SHA256(Wireshark-win64-3.0.5.exe)=888ff1269fe7ad887fe03d066094933df5c721100035ae76a85278b1380f8616 RIPEMD160(Wireshark-win64-3.0.5.exe)=a7e62a6b3734100868dc48fbdd535c003f664b97 SHA1(Wireshark-win64-3.0.5.exe)=5155cad98750ca9c03b06ff5cfb130a7271e9186 Wireshark-win32-3.0.5.msi: 41963520 bytes SHA256(Wireshark-win32-3.0.5.msi)=18c1c53edaa007399792bcce0f1c4032071f4977772f0a4a9740c9f591d26823 RIPEMD160(Wireshark-win32-3.0.5.msi)=4b1ffe59a77740229a1095740901752144d507b7 SHA1(Wireshark-win32-3.0.5.msi)=7eece0f67df9768baa1cce6142489b9330267295 Wireshark-win64-3.0.5.msi: 47185920 bytes SHA256(Wireshark-win64-3.0.5.msi)=8a9ab13a84e1399428b6bfb8ede32d620f617963de263ff419a1cbc7ea14d900 RIPEMD160(Wireshark-win64-3.0.5.msi)=b9c53c0fa201f8d16d5425ad6e5471a69095aecf SHA1(Wireshark-win64-3.0.5.msi)=1057b78c0597741a67e1b117159167fd333864ce WiresharkPortable_3.0.5.paf.exe: 35752672 bytes SHA256(WiresharkPortable_3.0.5.paf.exe)=887f6a287d9480dd617d81e7c4d8676dca0a51fc680d06ce61e7e2a505e325eb RIPEMD160(WiresharkPortable_3.0.5.paf.exe)=516200ea607275fe32d37d3d66fa7ec92ad51301 SHA1(WiresharkPortable_3.0.5.paf.exe)=cea2522c37e37d49b9699e921fdbc1df817bdae0 Wireshark 3.0.5 Intel 64.dmg: 93127687 bytes SHA256(Wireshark 3.0.5 Intel 64.dmg)=21bffc033dfbee74d30c6209dfa7ed57107cb7dd9d394fee579a333cddb746e6 RIPEMD160(Wireshark 3.0.5 Intel 64.dmg)=3767a858d273440301fb047dadf4f8603b48a7f8 SHA1(Wireshark 3.0.5 Intel 64.dmg)=3d6ebee21ddbe74814d45d879bc567de2a2213b9 You can validate these hashes using the following commands (among others): Windows: certutil -hashfile Wireshark-win64-x.y.z.exe SHA256 Linux (GNU Coreutils): sha256sum wireshark-x.y.z.tar.xz macOS: shasum -a 256 "Wireshark x.y.z Intel 64.dmg" Other: openssl sha256 wireshark-x.y.z.tar.xz
Attachment:
signature.asc
Description: OpenPGP digital signature
- Prev by Date: Re: [Wireshark-dev] Any solutions to problems running QT-Based Wireshark on CentOS 7.5
- Next by Date: [Wireshark-dev] Wireshark review to release
- Previous by thread: Re: [Wireshark-dev] Any solutions to problems running QT-Based Wireshark on CentOS 7.5
- Next by thread: [Wireshark-dev] Wireshark review to release
- Index(es):