Wireshark-users: [Wireshark-users] Wireshark 3.2.7 is now available
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Thu, 24 Sep 2020 08:53:53 -0700
I'm proud to announce the release of Wireshark 3.2.7. 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.9997. They previously shipped with Npcap 0.9994. The Windows installers now ship with Qt 5.12.9. They previously shipped with Qt 5.12.8. Bug Fixes The following vulnerabilities have been fixed: • wnpa-sec-2020-11[1] MIME Multipart dissector crash. Bug 16741[2]. Fixed in master: 2411eae9ed Fixed in master-3.2: 21f082cb6e Fixed in master-3.0: 14e274f3be Fixed in master-2.6: 5803c7b87b • wnpa-sec-2020-12[3] TCP dissector crash. Bug 16816[4]. Fixed in master: c4634b1e99 Fixed in master-3.2: e9b727595b Fixed in master-3.0: 7f3fe6164a Fixed in master-2.6: 9d7ab8b46f • wnpa-sec-2020-13[5] BLIP dissector crash. Bug 16866[6]. Fixed in master: 4a94842710 Fixed in master-3.2: 594d312b12 Fixed in master-3.0: 2fb6002559 Fixed in master-2.6: n/a The following bugs have been fixed: • HTTP dissector fails to display correct UTF-16 XML Bug 9069[7]. • TFTP dissector does not track conversations correctly. Source file and Destination File redundant or disagree. Bug 10305[8]. • Dissector skips DICOM command Bug 13110[9]. • Editcap time adjustment doesn’t work when both infile and outfile are ERF Bug 16578[10]. • dissect_tds7_colmetadata_token() has wrong return value if count is 0 Bug 16682[11]. • "total block length … is too small" for Systemd Journal Export Block Bug 16734[12]. • MNC 11 is showing Mobile Network Code (MNC): NTT DoCoMo Tokai Inc. (11) But its belonging to Rakuten Network Bug 16755[13]. • DICOM object extraction: discrepancy between tshark and wireshark Bug 16771[14]. • S1-U data forwarding info and S103 PDN data forwarding info IE’s showing improper value Bug 16777[15]. • Wireshark crashes while opening a capture Bug 16780[16]. • Changing preferences via Decode As does not call callback Bug 16787[17]. • Decoding of PFCP IE 'Remote GTP-U Peer' is incorrect Bug 16805[18]. • Ng-enb not decoded correctly for Target Identification IE for GTPV2 Bug 16822[19]. • The client timestamp is parsed error for Google QUIC (version Q039) Bug 16839[20]. • NAS-5G : PDU session reactivation result Bug 16842[21]. • Wireshark fails to detect libssh >= 0.9.5 Bug 16845[22]. 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 Aeron, AFP, BLIP, BSSMAP, C12.22, DICOM, E.212, GQUIC, GSM A RR, GTPv2, GVSP, IPX SAP, MIME Multipart, MMS, NAS-5GS, NCP, NDS, PFCP, PROFINET, Q.708, Q.933, RTCP, S1AP, TACACS+, TCP, TDS, TDS7, X2AP, and XML New and Updated Capture File 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[23] 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[24] 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[25]. Bugs and feature requests can be reported on the bug tracker[26]. Frequently Asked Questions A complete FAQ is available on the Wireshark web site[27]. Last updated 2020-09-23 21:05:39 UTC References 1. https://www.wireshark.org/security/wnpa-sec-2020-11 2. https://gitlab.com/wireshark/wireshark/-/issues/16741 3. https://www.wireshark.org/security/wnpa-sec-2020-12 4. https://gitlab.com/wireshark/wireshark/-/issues/16816 5. https://www.wireshark.org/security/wnpa-sec-2020-13 6. https://gitlab.com/wireshark/wireshark/-/issues/16866 7. https://gitlab.com/wireshark/wireshark/-/issues/9069 8. https://gitlab.com/wireshark/wireshark/-/issues/10305 9. https://gitlab.com/wireshark/wireshark/-/issues/13110 10. https://gitlab.com/wireshark/wireshark/-/issues/16578 11. https://gitlab.com/wireshark/wireshark/-/issues/16682 12. https://gitlab.com/wireshark/wireshark/-/issues/16734 13. https://gitlab.com/wireshark/wireshark/-/issues/16755 14. https://gitlab.com/wireshark/wireshark/-/issues/16771 15. https://gitlab.com/wireshark/wireshark/-/issues/16777 16. https://gitlab.com/wireshark/wireshark/-/issues/16780 17. https://gitlab.com/wireshark/wireshark/-/issues/16787 18. https://gitlab.com/wireshark/wireshark/-/issues/16805 19. https://gitlab.com/wireshark/wireshark/-/issues/16822 20. https://gitlab.com/wireshark/wireshark/-/issues/16839 21. https://gitlab.com/wireshark/wireshark/-/issues/16842 22. https://gitlab.com/wireshark/wireshark/-/issues/16845 23. https://www.wireshark.org/download.html#thirdparty 24. https://ask.wireshark.org/ 25. https://www.wireshark.org/lists/ 26. https://bugs.wireshark.org/ 27. https://www.wireshark.org/faq.html Digests wireshark-3.2.7.tar.xz: 31659996 bytes SHA256(wireshark-3.2.7.tar.xz)=be832fb86d9c455c5be8b225a755cdc77cb0e92356bdfc1fe4b000d93f7d70da RIPEMD160(wireshark-3.2.7.tar.xz)=81787ab8814cba0452da9cb45fcfd988da5ec587 SHA1(wireshark-3.2.7.tar.xz)=b564c2e729066cb7c952463fef6163e23a5fea1e Wireshark-win64-3.2.7.exe: 60139752 bytes SHA256(Wireshark-win64-3.2.7.exe)=d418b047d8f77d6ae804a5121d18d941bc45ca47c30f553d0034d6136c3069a4 RIPEMD160(Wireshark-win64-3.2.7.exe)=9d13f6ff774c53b8132e699632981fcb4a62cfb9 SHA1(Wireshark-win64-3.2.7.exe)=fb729e381b42583358fdc7459d1558c6ee640925 Wireshark-win32-3.2.7.exe: 54971224 bytes SHA256(Wireshark-win32-3.2.7.exe)=5b41010a28857bf842ddd671d13896ff7a186144e792e674ac0b5d87b50e3934 RIPEMD160(Wireshark-win32-3.2.7.exe)=badf7e3b4039bdb55e1f93c4bd4d2ec9163976d4 SHA1(Wireshark-win32-3.2.7.exe)=523aba9b39c50e2d491912778beb604209bc7053 Wireshark-win64-3.2.7.msi: 48414720 bytes SHA256(Wireshark-win64-3.2.7.msi)=bbf11f1b14f862ce05880529766310a46d9f9edfc614beec00b6f6ac9e0c6855 RIPEMD160(Wireshark-win64-3.2.7.msi)=eaaa0ea72e89bb28a888fe4e01f732f9f5801479 SHA1(Wireshark-win64-3.2.7.msi)=5faac479c2fae5e59b2607ba9b86bad61e2f63da Wireshark-win32-3.2.7.msi: 43147264 bytes SHA256(Wireshark-win32-3.2.7.msi)=dff48de86ed11197bc5b8f033f11cd650d94ea2d458dda23429ad804be922ca3 RIPEMD160(Wireshark-win32-3.2.7.msi)=9749531a662f670dc4d6e87af1558c18186e1106 SHA1(Wireshark-win32-3.2.7.msi)=2f8512a4e1d252cb134362148c1ab46e43f152a5 WiresharkPortable_3.2.7.paf.exe: 36699080 bytes SHA256(WiresharkPortable_3.2.7.paf.exe)=2eb3ded78c1c800e088359828e221fc65d004559dd0ec00fdaecefbf7600a523 RIPEMD160(WiresharkPortable_3.2.7.paf.exe)=5cfb43dfe5fdd831587bb0ac96e0c153a155c8a6 SHA1(WiresharkPortable_3.2.7.paf.exe)=5a34d03c9fbd3e497c2f6cf25402003881ce6934 Wireshark 3.2.7 Intel 64.dmg: 97732672 bytes SHA256(Wireshark 3.2.7 Intel 64.dmg)=1347138534c6d9adb2ee1af7898cac2248b63bfb1ac6afee54e17725ab333106 RIPEMD160(Wireshark 3.2.7 Intel 64.dmg)=173acd594c6ac6e58c898a813f4f0749108799ad SHA1(Wireshark 3.2.7 Intel 64.dmg)=08100d6f479b20075d03f89dbec4b1364264a625 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-users] Remote Developer Den, July 2020
- Next by Date: [Wireshark-users] Remote Capture in Wireshark of a server located in multiple hopes away
- Previous by thread: [Wireshark-users] Remote Developer Den, July 2020
- Next by thread: [Wireshark-users] Remote Capture in Wireshark of a server located in multiple hopes away
- Index(es):