Congratulations! That's a great achievement! Alex
On Wed, Apr 21, 2021, 20:49 Gerald Combs <ger...@wireshark.org> wrote: > I'm proud to announce the release of Wireshark 3.4.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 > > Bug Fixes > > The following vulnerabilities have been fixed: > > • wnpa-sec-2021-04[1] MS-WSP dissector excessive memory > consumption. Issue 17331[2]. > > The following bugs have been fixed: > > • TShark does not print GeoIP information Issue 14691[3]. > > • TShark error when piping to "head" Issue 16192[4]. > > • Parts of ASCII representation in Packet Bytes pane are missing > Issue 17087[5]. > > • Buildbot crash output: fuzz-2021-02-22-1012761.pcap Issue > 17254[6]. > > • NDPE attribute of NAN packet is not dissected Issue 17278[7]. > > • TECMP: reserved flag interpreted as part of timestamp Issue > 17279[8]. > > • Master branch does not compile at least with gcc-11 Issue > 17281[9]. > > • DNS IXFR/AXFR multiple response Issue 17293[10]. > > • File too large Issue 17301[11]. > > • Build fails with CMake 3.20 Issue 17314[12]. > > New and Updated Features > > New Protocol Support > > There are no new protocols in this release. > > Updated Protocol Support > > DECT, DNS, EAP, Kerberos, LDAP, MS-WSP, SMB2, Sysdig, TECMP, and WiFi > NAN > > 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[13] 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[14] 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[15]. > > Issues and feature requests can be reported on the issue tracker[16]. > > Frequently Asked Questions > > A complete FAQ is available on the Wireshark web site[17]. > > Last updated 2021-04-21 17:17:37 UTC > > References > > 1. https://www.wireshark.org/security/wnpa-sec-2021-04 > 2. https://gitlab.com/wireshark/wireshark/-/issues/17331 > 3. https://gitlab.com/wireshark/wireshark/-/issues/14691 > 4. https://gitlab.com/wireshark/wireshark/-/issues/16192 > 5. https://gitlab.com/wireshark/wireshark/-/issues/17087 > 6. https://gitlab.com/wireshark/wireshark/-/issues/17254 > 7. https://gitlab.com/wireshark/wireshark/-/issues/17278 > 8. https://gitlab.com/wireshark/wireshark/-/issues/17279 > 9. https://gitlab.com/wireshark/wireshark/-/issues/17281 > 10. https://gitlab.com/wireshark/wireshark/-/issues/17293 > 11. https://gitlab.com/wireshark/wireshark/-/issues/17301 > 12. https://gitlab.com/wireshark/wireshark/-/issues/17314 > 13. https://www.wireshark.org/download.html#thirdparty > 14. https://ask.wireshark.org/ > 15. https://www.wireshark.org/lists/ > 16. https://gitlab.com/wireshark/wireshark/-/issues > 17. https://www.wireshark.org/faq.html > > > Digests > > wireshark-3.4.5.tar.xz: 32300144 bytes > > SHA256(wireshark-3.4.5.tar.xz)=de1aafd100a1e1207c850d180e97dd91ab8da0f5eb6beec545f725cdb145d333 > RIPEMD160(wireshark-3.4.5.tar.xz)=9f97f8bd34d09cbe6afc2bf655b44940a90154b6 > SHA1(wireshark-3.4.5.tar.xz)=d01a9b5f58206fb458fe9fc2dac88ad0ea7152ce > > Wireshark-win32-3.4.5.exe: 56531712 bytes > > SHA256(Wireshark-win32-3.4.5.exe)=bc46bdc14dac4c67033bc5ad5590e4b221d5724ba28569b9134c13528fa37fed > > RIPEMD160(Wireshark-win32-3.4.5.exe)=3ff3fc99c3abd8d1e1fb143140a2e51b3cd66473 > SHA1(Wireshark-win32-3.4.5.exe)=14b1372e0a1e1bd709cb0c10d1b21d92bb6a5310 > > Wireshark-win64-3.4.5.exe: 61475448 bytes > > SHA256(Wireshark-win64-3.4.5.exe)=e6a7f8b48221b642b8b0911dd1519d3436a5a90e99525e80f1764bf4938b35e5 > > RIPEMD160(Wireshark-win64-3.4.5.exe)=047d9c8b23cd7522f2bd1bf03b28c53e0bdfa0d5 > SHA1(Wireshark-win64-3.4.5.exe)=501f87fdc7aeaed6c704ee5a4974f02f13b9d7b0 > > Wireshark-win32-3.4.5.msi: 44761088 bytes > > SHA256(Wireshark-win32-3.4.5.msi)=381aeaac7fbd7d7fbfc45292caf93de2bdbf46f57fa30e6af0d6522ba5350ffb > > RIPEMD160(Wireshark-win32-3.4.5.msi)=243ffdf35fc3d92cbf977558441fc3de074815be > SHA1(Wireshark-win32-3.4.5.msi)=ee6ae0bd87052fd1e8a59102df7351a557b27c5d > > Wireshark-win64-3.4.5.msi: 49807360 bytes > > SHA256(Wireshark-win64-3.4.5.msi)=e6a94b71faaf29c5c3804dcb6aabb26d1d7bf3cbece502fc1f119830d3ea8abf > > RIPEMD160(Wireshark-win64-3.4.5.msi)=527b4aa7eff5bd90ba305ef927276cef645cdb4b > SHA1(Wireshark-win64-3.4.5.msi)=c41d1dbb84b77987fcde157d6dddd7b954a186af > > WiresharkPortable_3.4.5.paf.exe: 38402968 bytes > > SHA256(WiresharkPortable_3.4.5.paf.exe)=210c688bf7f4efb0995e25939de64d611faf6400798f6eb4b3c9c1f168f522c5 > > RIPEMD160(WiresharkPortable_3.4.5.paf.exe)=a61a7f8de529a274b256a3c407d04a3c9564d542 > > SHA1(WiresharkPortable_3.4.5.paf.exe)=2b91c30068d9504339dde4d9ed603f71f45ac15f > > Wireshark 3.4.5 Intel 64.dmg: 130985157 bytes > SHA256(Wireshark 3.4.5 Intel > 64.dmg)=d5565b525d71a9effe64ff4a84b896c9ce0d0d34959a8e9d2f7093dcf3c8ca68 > RIPEMD160(Wireshark 3.4.5 Intel > 64.dmg)=933200a194579946dcb5b42b018fc0abbe6375db > SHA1(Wireshark 3.4.5 Intel 64.dmg)=c0b6bf94349451230724c1e320750136f82d4f4b > > 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 > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-...@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
