Wireshark · Wireshark-users: [Wireshark-users] Wireshark 3.0.2 is now available

[Gerald Combs <gerald@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.0.2.


 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 Qt 5.12.3. They previously
      shipped with Qt 5.12.1.

    • The Windows installers now ship with Npcap 0.995. They previously
      shipped with Npcap 0.992.

    • The macOS packages are now notarized[1].

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2019-19[2] Wireshark dissection engine crash. Bug
       15778[3].

   The following bugs have been fixed:

     • Add (IETF) QUIC Dissector. Bug 13881[4].

     • Wireshark Hangs on startup initializing external capture plugins.
       Bug 14657[5].

     • [oss-fuzz] ERROR: Adding ospf.v3.prefix.options.nu would put more
       than 1000000 items in the tree — possible infinite loop. Bug
       14978[6].

     • Wireshark can call extcap with empty multicheck argument. Bug
       15065[7].

     • CMPv2 KUR message disection gives unexpected value for
       serialNumber under OldCertId fields. Bug 15154[8].

     • "(Git Rev Unknown from unknown)" in version string for official
       tarball. Bug 15544[9].

     • External extcap does not get all arguments sometimes. Bug
       15586[10].

     • Help file doesn’t display for extcap interfaces. Bug 15592[11].

     • Buildbot crash output: randpkt-2019-03-14-4670.pcap. Bug
       15604[12].

     • Building only libraries on windows fails due to CLEAN_C_FILES
       empty. Bug 15662[13].

     • Statistics→Conversations→TCP→Follow Stream - incorrect behavior.
       Bug 15672[14].

     • Wrong NTP timestamp for RTCP XR RR packets (hf_rtcp_xr_timestamp
       field). Bug 15687[15].

     • ws_pipe: leaks pipe handles on errors. Bug 15689[16].

     • Build issue in Wireshark - 3.0.1 on RHEL6. Bug 15706[17].

     • ISAKMP: Segmentation fault with non-hex string for IKEv1
       Decryption Table Initiator Cookie. Bug 15709[18].

     • extcap: non-boolean call arguments can be appended without value
       on selector Reload. Bug 15725[19].

     • Incorrectly interpreted format of MQTT PUBLISH payload data. Bug
       15738[20].

     • print.c: Memory leak in ek_check_protocolfilter. Bug 15758[21].

     • IETF QUIC dissector incorrectly parses retry packet. Bug
       15764[22].

     • Bacnet(app): fix wrong value for id 183 (logging-device →
       logging-object). Bug 15767[23].

     • The SMB2 code to look up decryption keys by session ID assumes
       it’s running on a little-endian machine. Bug 15772[24].

     • tshark -G folders leaves mmdbresolve process behind. Bug
       15777[25].

     • Dissector bug, protocol TLS - failed assertion "data". Bug
       15780[26].

     • WSMP : header_opt_ind field is not correctly set. Bug 15786[27].

  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

   BACapp, DDP, EPL, Frame, IEEE 802.11, IS-IS CLV, ISAKMP, K12, KNXIP,
   MQTT, PNIO, QUIC, RTCP XR RR, SCTP, SMB2, TDS, TLS, WSMP, and ZEBRA

  New and Updated Capture File Support

   pcapng

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

  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[29] 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/[30]

  Community support is available on Wireshark’s Q&A site[31] 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[32].

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

  Official Wireshark training and certification are available from
  Wireshark University[34].

 Frequently Asked Questions

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

  Last updated 2019-05-22 17:31:02 UTC

 References

   1. https://developer.apple.com/documentation/security/notarizing_your
  _app_before_distribution
   2. https://www.wireshark.org/security/wnpa-sec-2019-19
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15778
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13881
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14657
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14978
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15065
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15154
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15544
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15586
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15592
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15604
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15662
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15672
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15687
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15689
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15706
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15709
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15725
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15738
  21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15758
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15764
  23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15767
  24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15772
  25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15777
  26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15780
  27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15786
  28. https://www.wireshark.org/download.html
  29. https://www.wireshark.org/download.html#thirdparty
  30. https://www.wireshark.org/docs/
  31. https://ask.wireshark.org/
  32. https://www.wireshark.org/lists/
  33. https://bugs.wireshark.org/
  34. http://www.wiresharktraining.com/
  35. https://www.wireshark.org/faq.html


Digests

wireshark-3.0.2.tar.xz: 30910100 bytes
SHA256(wireshark-3.0.2.tar.xz)=7e1ec5664a0dba4493d8729f9922378bdd05040fb159c2b03b42111efda2e53b
RIPEMD160(wireshark-3.0.2.tar.xz)=52c36f04fe8858a2aa7e6b9a682f658b392d432d
SHA1(wireshark-3.0.2.tar.xz)=64d18b3c6faa1cb2052562657f610946334ac643

Wireshark-win64-3.0.2.exe: 59287984 bytes
SHA256(Wireshark-win64-3.0.2.exe)=27d15f43091e002d454fb63f8c438fe4b32a86b57c02c6cb83ef36bdbfaefe09
RIPEMD160(Wireshark-win64-3.0.2.exe)=c1eb04a4c0a7c9d7674580e51d531c240fad7aea
SHA1(Wireshark-win64-3.0.2.exe)=9a9cc106eac23276af5290673a8af12e1d58a0de

Wireshark-win32-3.0.2.exe: 54112336 bytes
SHA256(Wireshark-win32-3.0.2.exe)=ea4f9a4b55bed282408d595bf2e86951014e108144662f8add51cb0a7ad034ed
RIPEMD160(Wireshark-win32-3.0.2.exe)=11ad7ad243ae63cb1dbe1f92be20fc0b707c34f2
SHA1(Wireshark-win32-3.0.2.exe)=f1941f085a1db8635327701c0ab4ce925ffd3f8c

Wireshark-win32-3.0.2.msi: 42033152 bytes
SHA256(Wireshark-win32-3.0.2.msi)=a2d8c37ead1824f1bc19bff2e37fdde777e0619396eace07b36a071b5ecfa5ee
RIPEMD160(Wireshark-win32-3.0.2.msi)=902e5f87d0208c188fc1e4758ae4ec0da8df0852
SHA1(Wireshark-win32-3.0.2.msi)=e070636edb40cd30f182b4459a23e85eff143b7f

Wireshark-win64-3.0.2.msi: 47210496 bytes
SHA256(Wireshark-win64-3.0.2.msi)=6e3e21c399ce84793616982f42c3277061d7593c4fc4a6899ea2f31381537ddd
RIPEMD160(Wireshark-win64-3.0.2.msi)=b9d9f144eeaadbd15468bdaeadcf6661c2a0e350
SHA1(Wireshark-win64-3.0.2.msi)=73452542d33a17f30f604ef99aafc298ba834041

WiresharkPortable_3.0.2.paf.exe: 35804560 bytes
SHA256(WiresharkPortable_3.0.2.paf.exe)=eb43c5f9dcd852e39b91837ccf26b940b89549e210f9d78df15e6ebbdcbc0d9d
RIPEMD160(WiresharkPortable_3.0.2.paf.exe)=08a409043a0c1fcc50396cf73047c9f2033a234c
SHA1(WiresharkPortable_3.0.2.paf.exe)=99eb79a9b3ed9eae1a50f384870901d77ca10848

Wireshark 3.0.2 Intel 64.dmg: 87206906 bytes
SHA256(Wireshark 3.0.2 Intel
64.dmg)=2e32ed900bc0bb85430ebe45eef39c5097423eb8cb3a7bd4b08e704f599ab430
RIPEMD160(Wireshark 3.0.2 Intel
64.dmg)=e3c82a44cc3d8200654affd4404970183733c912
SHA1(Wireshark 3.0.2 Intel 64.dmg)=fc5b93bcf481ddef2015677e4094ef10fc3198a8

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