Wireshark-dev: [Wireshark-dev] Wireshark 3.0.13 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Wed, 12 Aug 2020 12:51:33 -0700
I'm proud to announce the release of Wireshark 3.0.13. 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: The following bugs have been fixed: • Dissector for ASTERIX Category 001 / 210 does not recognize bit 1 as extension. Bug 16662[1]. • "invalid timestamp" for Systemd Journal Export Block. Bug 16664[2]. • Short IMSIs (5 digits) lead to wrong decoding+warning. Bug 16676[3]. • Decoding of PFCP IE 'PFD Contents' results in "malformed packet". Bug 16704[4]. • RFH2 Header with 32 or less bytes of NameValue will not parse out that info. Bug 16733[5]. • CDP: Port ID TLV followed by Type 1009 TLV triggers [Malformed Packet]. Bug 16742[6]. • tshark crashed when processing opcda. Bug 16746[7]. • tshark with --export-dicom gives “Segmentation fault (core dumped)”. Bug 16748[8]. 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 ASTERIX, BSSAP, CDP, DCERPC SPOOLSS, DCOM, DVB-S2, E.212, GBCS, GSM RR, GSM SMS, IEEE 802.11, MQ, Nano, NIS+, PFCP, RTPS, systemd Journal, TDS, TN3270, and TN5250 New and Updated Capture File Support There is no new or updated capture file support in this release. New and Updated Capture Interfaces support pcapng 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[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/ Community support is available on Wireshark’s Q&A site[10] 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[11]. Bugs and feature requests can be reported on the bug tracker[12]. Frequently Asked Questions A complete FAQ is available on the Wireshark web site[13]. Last updated 2020-08-12 17:56:01 UTC References 1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16662 2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16664 3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16676 4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16704 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16733 6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16742 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16746 8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16748 9. https://www.wireshark.org/download.html#thirdparty 10. https://ask.wireshark.org/ 11. https://www.wireshark.org/lists/ 12. https://bugs.wireshark.org/ 13. https://www.wireshark.org/faq.html Digests wireshark-3.0.13.tar.xz: 30928312 bytes SHA256(wireshark-3.0.13.tar.xz)=0463b0f424d0962933ae681b3d5580780906c02f08a3ab852b787999b2884c47 RIPEMD160(wireshark-3.0.13.tar.xz)=33653c23fc4ac5ce1d28e926d642a86237ed1573 SHA1(wireshark-3.0.13.tar.xz)=3f5a418cdd0f4ab6dd7b95d3ca8f1a0e85af9927 Wireshark-win64-3.0.13.exe: 59297592 bytes SHA256(Wireshark-win64-3.0.13.exe)=d9bf4bc656264d8b1e10a79c9d8d3edc112c218c39816e228bf3f882e5b5d32e RIPEMD160(Wireshark-win64-3.0.13.exe)=a5f0f0349001e46bd9b6bcc6fc1b91e785759517 SHA1(Wireshark-win64-3.0.13.exe)=9a473cd682547cd1d1860c6eb3dff00f4bbef769 Wireshark-win32-3.0.13.exe: 54085432 bytes SHA256(Wireshark-win32-3.0.13.exe)=1c61fe5ec90f20319d7b46e115c84d0a541a079ba8d1dae0303833f64a8da458 RIPEMD160(Wireshark-win32-3.0.13.exe)=d0a6cf8f5b933f78650de0da8ee3165f20c3afea SHA1(Wireshark-win32-3.0.13.exe)=625df6bd716a3a0c6ae26d3d872c00ccb3374ea2 Wireshark-win32-3.0.13.msi: 42082304 bytes SHA256(Wireshark-win32-3.0.13.msi)=11ea61c4ff1281b838de80309f82c38dc515216d245463b9d87b5857a50c0208 RIPEMD160(Wireshark-win32-3.0.13.msi)=1161abbf5ea69f64dc4c2e8a62098ffffe80cb58 SHA1(Wireshark-win32-3.0.13.msi)=8ba6a500d0ec8ae6edc1fa02343a9bfa8a8b58d9 Wireshark-win64-3.0.13.msi: 47288320 bytes SHA256(Wireshark-win64-3.0.13.msi)=e411cbb6fe20432f8e686713fccb61f9e18ec7a1d2cce329dd8bcd916ba4ac21 RIPEMD160(Wireshark-win64-3.0.13.msi)=243659938004f15c16b830b3d2ff29f2490b1196 SHA1(Wireshark-win64-3.0.13.msi)=898b401a69c82e6c975970b30ca60010b3511779 WiresharkPortable_3.0.13.paf.exe: 35851856 bytes SHA256(WiresharkPortable_3.0.13.paf.exe)=bd5f0dc55cdd3c7d393c6dce75a7cb422c6af88cf9d13a4aecab3b4f345525b5 RIPEMD160(WiresharkPortable_3.0.13.paf.exe)=6f1c8d4ca53142ed64872ecccf2ebb9b502d059e SHA1(WiresharkPortable_3.0.13.paf.exe)=d663fc6137045b8fa120eb6f83694320ad2dbe2a Wireshark 3.0.13 Intel 64.dmg: 93148932 bytes SHA256(Wireshark 3.0.13 Intel 64.dmg)=548bb2e572232f9a29267ddca28eb79aae632bf9b4af0df69f4adf8d82ae557a RIPEMD160(Wireshark 3.0.13 Intel 64.dmg)=4bf2e9757b0f1ab16da0d48e8f56c8e2c21e6e39 SHA1(Wireshark 3.0.13 Intel 64.dmg)=e926d30254b031f62fc687c4c4b5c0dd1365ddbd 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: [Wireshark-dev] Wireshark 3.2.6 is now available
- Next by Date: Re: [Wireshark-dev] [Wireshark-users] The Wireshark wiki has a new home
- Previous by thread: [Wireshark-dev] Wireshark 3.2.6 is now available
- Next by thread: [Wireshark-dev] Filtering on a field when there is more than one such field in a Wi-Fi packet
- Index(es):