Wireshark-announce: [Wireshark-announce] Wireshark 3.0.14 is now available
From: Wireshark announcements <[email protected]>
Date: Thu, 24 Sep 2020 08:56:46 -0700
I'm proud to announce the release of Wireshark 3.0.14.


 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

  This is expected to be the final release of the Wireshark 3.0 branch.
  It will reach its official end of life when Wireshark 3.4.0 is
  released[1]. If you are still using Wireshark 3.0 you are encouraged
  to upgrade to Wireshark 3.2 or 3.4.

  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[2] MIME Multipart dissector crash. Bug 16741[3].
       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[4] TCP dissector crash. Bug 16816[5]. 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[6] BLIP dissector crash. Bug 16866[7]. 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:

     • Buildbot crash output: randpkt-2019-04-01-28345.pcap Bug
       15661[8].

     • Buildbot crash output: fuzz-2020-07-28-5905.pcap Bug 16741[9].

     • S1-U data forwarding info and S103 PDN data forwarding info IE’s
       showing improper value Bug 16777[10].

     • The client timestamp is parsed error for Google QUIC (version
       Q039) Bug 16839[11].

     • Wireshark fails to detect libssh >= 0.9.5 Bug 16845[12].

  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

   AARP, BLIP, BSSMAP, GQUIC, GSM A RR, GTPv2, MIME Multipart, NCP, NDS,
   PFCP, PROFINET, Q.933, S1AP, TACACS+, TCP, and X2AP

  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.

  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].

  Bugs and feature requests can be reported on the bug tracker[16].

 Frequently Asked Questions

  A complete FAQ is available on the Wireshark web site[17].

  Last updated 2020-09-23 21:05:30 UTC

 References

   1. https://gitlab.com/wireshark/editor-wiki/-/wikis/Development/LifeC
  ycle#end-of-life-planning
   2. https://www.wireshark.org/security/wnpa-sec-2020-11
   3. https://gitlab.com/wireshark/wireshark/-/issues/16741
   4. https://www.wireshark.org/security/wnpa-sec-2020-12
   5. https://gitlab.com/wireshark/wireshark/-/issues/16816
   6. https://www.wireshark.org/security/wnpa-sec-2020-13
   7. https://gitlab.com/wireshark/wireshark/-/issues/16866
   8. https://gitlab.com/wireshark/wireshark/-/issues/15661
   9. https://gitlab.com/wireshark/wireshark/-/issues/16741
  10. https://gitlab.com/wireshark/wireshark/-/issues/16777
  11. https://gitlab.com/wireshark/wireshark/-/issues/16839
  12. https://gitlab.com/wireshark/wireshark/-/issues/16845
  13. https://www.wireshark.org/download.html#thirdparty
  14. https://ask.wireshark.org/
  15. https://www.wireshark.org/lists/
  16. https://bugs.wireshark.org/
  17. https://www.wireshark.org/faq.html


Digests

wireshark-3.0.14.tar.xz: 30932840 bytes
SHA256(wireshark-3.0.14.tar.xz)=c994d6931d60d82908f71702f886c27b996a4033ff959f0b547e785e5dbe3abe
RIPEMD160(wireshark-3.0.14.tar.xz)=f1e743fb832c46a78c6bb93b93dff529b5f7929c
SHA1(wireshark-3.0.14.tar.xz)=13ddc4f61e873377c06af4b4d30e3e54bea7cc4d

Wireshark-win32-3.0.14.exe: 54097856 bytes
SHA256(Wireshark-win32-3.0.14.exe)=f246b1771f151ae9981378950ebde1a01c5582d22edbcc287ac78714338c9d7d
RIPEMD160(Wireshark-win32-3.0.14.exe)=1d6173b282a6089b089e0fed4259e6f25f510ca2
SHA1(Wireshark-win32-3.0.14.exe)=d8c14322a71678e28f7ba8fe91e7e71815e342f6

Wireshark-win64-3.0.14.exe: 59301384 bytes
SHA256(Wireshark-win64-3.0.14.exe)=781bf76c4fa8ad1f95425052abeda2fa40344a9c8582ee0e43fc43947c1121cf
RIPEMD160(Wireshark-win64-3.0.14.exe)=ff56f448d44e91c5570a10dbf0caa08ab14bd22b
SHA1(Wireshark-win64-3.0.14.exe)=3dc92864212950c664ecb9b3e65ae565a6996b8e

Wireshark-win64-3.0.14.msi: 47284224 bytes
SHA256(Wireshark-win64-3.0.14.msi)=90176a1b0189387163eb666732513e3c456dd42f56f46163b63c0ae1ebd5b266
RIPEMD160(Wireshark-win64-3.0.14.msi)=573e91d1a43c4c9b10e75767f489256d54366e10
SHA1(Wireshark-win64-3.0.14.msi)=32fa4a21c5274b39d2836fd4c011e2ade96a6fb3

Wireshark-win32-3.0.14.msi: 42098688 bytes
SHA256(Wireshark-win32-3.0.14.msi)=2e4772c363622eecad0805464fbddc3ab78f7623da5d2c6202ee402f914e37ef
RIPEMD160(Wireshark-win32-3.0.14.msi)=e3d5785db8f593df18f38b99ef66da3bcec14fdd
SHA1(Wireshark-win32-3.0.14.msi)=9a27d8e3d00fd5491d9b2880ae637bcadc04c8ff

WiresharkPortable_3.0.14.paf.exe: 35857240 bytes
SHA256(WiresharkPortable_3.0.14.paf.exe)=9fa17fc90fd701821aa0d0504e015e3f5267a0a030199a7ec4be92e15e4902e8
RIPEMD160(WiresharkPortable_3.0.14.paf.exe)=e822509021461d099c824a033dba01badab77ebc
SHA1(WiresharkPortable_3.0.14.paf.exe)=8424d7f29432d62348208248a1d9f33ff59adf85

Wireshark 3.0.14 Intel 64.dmg: 93189905 bytes
SHA256(Wireshark 3.0.14 Intel 64.dmg)=87e0929f7d8ad94154cdbed9dde73008dc46172edd1293dc45c2dbcec317f3ca
RIPEMD160(Wireshark 3.0.14 Intel 64.dmg)=40c62f5897e62f65aae436596e5d3352ef2608dd
SHA1(Wireshark 3.0.14 Intel 64.dmg)=ea983ef45236cddf0195ee71ab689ca1b2fba6ca

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