Wireshark-dev: [Wireshark-dev] Wireshark 3.0.4 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 11 Sep 2019 15:38:28 -0700
I'm proud to announce the release of Wireshark 3.0.4. 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 Npcap 0.9983. They previously shipped with Npcap 0.996. • The macOS installer now ships with Qt 5.12.3. It previously shipped with Qt 5.12.4. Bug Fixes The following vulnerabilities have been fixed: • wnpa-sec-2019-21[1] Gryphon dissector infinite loop. Bug 16020[2]. The following bugs have been fixed: • Coloring Rules dialog - enable/disable coloring rule issues. Bug 15153[3]. • Enabling Time-Of-Day in IO Graph causes the x-axis origin to be set to 01.01.1970. Bug 15247[4]. • Wireshark GUI crashes when attempting to DnD multiple (possibly corrupted) pcapng files. Bug 15377[5]. • Buildbot crash output: randpkt-2019-06-14-14291.pcap. Bug 15848[6]. • 802.11 RSN IE may be shorter than 18 bytes. Bug 15905[7]. • Tshark outputs two data rate instead of one. Bug 15928[8]. • Typo in checkbox label at bottom of sshdump configuration screen (save parameters). Bug 15929[9]. • Invalid pkcs11_libs entry crashes on Windows. Bug 15957[10]. • Add additional text output for DNS types (DNSSEC). Bug 15970[11]. • LSD bittorent. Bug 15971[12]. • dfilter_macros is missing from Configuration Files article. Bug 15973[13]. • Pane configuration inconsistencies. Bug 15976[14]. • Packet list is sorted in reverse order after applying a display filter in Qt 5.13. Bug 15979[15]. • EAP-TLS fragments are repeatedly displayed. Bug 15982[16]. • Broken TLS handshake reassembly in EAP-TTLS with multiple TLS sessions. Bug 15983[17]. • Wireshark does not support USB packets with size greater than 256 KiB. Bug 15985[18]. • "Unable to drop files during capture." when drag’n’drop entry to create display filter or filter button. Bug 15986[19]. • Packet Bytes highlight for dns.qry.name.len and dns.count.labels off by one. Bug 15999[20]. • Segmentation fault in nfs_name_snoop_fh. Bug 16017[21]. • Changing the protocol preferences caused a crash. Bug 16019[22]. • DCERPC dissector broken for functions with only scalar variables. Bug 16022[23]. 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 BACnet, DCERPC, DNS, EAP, FC-dNS, Gryphon, IEEE 802.11, LSD, NFS, and Radiotap New and Updated Capture File Support CommView and PacketLogger 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[24]. 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[25] 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/[26] Community support is available on Wireshark’s Q&A site[27] 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[28]. Bugs and feature requests can be reported on the bug tracker[29]. Official Wireshark training and certification are available from Wireshark University[30]. Frequently Asked Questions A complete FAQ is available on the Wireshark web site[31]. Last updated 2019-09-11 19:31:50 UTC References 1. https://www.wireshark.org/security/wnpa-sec-2019-21 2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16020 3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15153 4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15247 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15377 6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15848 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15905 8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15928 9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15929 10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15957 11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15970 12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15971 13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15973 14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15976 15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15979 16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15982 17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15983 18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15985 19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15986 20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15999 21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16017 22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16019 23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16022 24. https://www.wireshark.org/download.html 25. https://www.wireshark.org/download.html#thirdparty 26. https://www.wireshark.org/docs/ 27. https://ask.wireshark.org/ 28. https://www.wireshark.org/lists/ 29. https://bugs.wireshark.org/ 30. http://www.wiresharktraining.com/ 31. https://www.wireshark.org/faq.html Digests wireshark-3.0.4.tar.xz: 30938336 bytes SHA256(wireshark-3.0.4.tar.xz)=773bd57df2aeae1694a0b7fbfb34283ba24799cfd6299eed696630fc9ebeecbf RIPEMD160(wireshark-3.0.4.tar.xz)=01a98122fbe701946088e0924a73333c2c79654b SHA1(wireshark-3.0.4.tar.xz)=e7cda5bc6fe885887fb4cffedb565373c760c987 Wireshark-win32-3.0.4.exe: 54079480 bytes SHA256(Wireshark-win32-3.0.4.exe)=dd5b1fc28fd14e8d916c138908c387cf73b7f45f5becec5ced8725c03c83be6c RIPEMD160(Wireshark-win32-3.0.4.exe)=5dfa388a68c94d95f2d2cfd2897c48f18a1069b7 SHA1(Wireshark-win32-3.0.4.exe)=148223adaad1a863bd94c43a675dec5afa82cc7c Wireshark-win64-3.0.4.exe: 59266704 bytes SHA256(Wireshark-win64-3.0.4.exe)=abe83ebcdf817bd5c97106670fe0e7e52b88c2b5978dfb66db10e7f780beb2e5 RIPEMD160(Wireshark-win64-3.0.4.exe)=7344763b16e0d710ad3eb6ca002b446410773bb1 SHA1(Wireshark-win64-3.0.4.exe)=1cdf965363b1a5b540239d3d9c317c44aaf1037f Wireshark-win64-3.0.4.msi: 47173632 bytes SHA256(Wireshark-win64-3.0.4.msi)=0aa9bc8b270a3d6a15b827d04cfe722c16c4615593ae89dd0be55c5d96eb56f2 RIPEMD160(Wireshark-win64-3.0.4.msi)=06d3fabeb97089614b05d2758f7388e1dc90bc88 SHA1(Wireshark-win64-3.0.4.msi)=42b47149fb56e6d0a17b6523e5b5f17bea233553 Wireshark-win32-3.0.4.msi: 41971712 bytes SHA256(Wireshark-win32-3.0.4.msi)=6670dda3b36188f0a4e093ee3b705edcea955067a04587e3fabe50a017e1c92f RIPEMD160(Wireshark-win32-3.0.4.msi)=43c1891fd8a3e21b60e97f5112cf51baf9c89d26 SHA1(Wireshark-win32-3.0.4.msi)=ac2f8e778e773d4510fba37bd9e3f89aa2ec4729 WiresharkPortable_3.0.4.paf.exe: 35763632 bytes SHA256(WiresharkPortable_3.0.4.paf.exe)=cf0a354148c5d01016fc2be15f821e9b4890809d36144c9ccf159e451d0255d3 RIPEMD160(WiresharkPortable_3.0.4.paf.exe)=a5a7d0c7c95c07f84ea6c72f8048391bda19b3d0 SHA1(WiresharkPortable_3.0.4.paf.exe)=21bb3bc33ff6e84bee696c96dcad21e427001610 Wireshark 3.0.4 Intel 64.dmg: 93133939 bytes SHA256(Wireshark 3.0.4 Intel 64.dmg)=82e5d5ac1379488e7de40965d68c0f66f50a409ebf1f0b94386d40d8b4b88951 RIPEMD160(Wireshark 3.0.4 Intel 64.dmg)=379474cbb5829d185a1a6cf02b736d0b3c7cc990 SHA1(Wireshark 3.0.4 Intel 64.dmg)=e7b4d0061169a8522a7a4db75d0e78c5ac8d9640 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] Switch master and PD Windows builders to Visual Studio 2019?
- Next by Date: [Wireshark-dev] Shard Output Format
- Previous by thread: Re: [Wireshark-dev] Switch master and PD Windows builders to Visual Studio 2019?
- Next by thread: [Wireshark-dev] Shard Output Format
- Index(es):