Wireshark-users: [Wireshark-users] Wireshark 3.0.6 is now available
From: Gerald Combs <[email protected]>
Date: Wed, 23 Oct 2019 11:51:44 -0700
I'm proud to announce the release of Wireshark 3.0.6.


 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

    • On macOS, Wireshark can now be installed by dropping Wireshark.app
      onto the Applications folder.

    • The macOS installer now ships with Qt 5.12.5. It previously
      shipped with Qt 5.12.3.

  Bug Fixes

   The following bugs have been fixed:

     • macOS installer uses wrong user ID. Bug 6991[1].

     • Using macosx-setup seems to prevent installing pre-built binary.
       Bug 11399[2].

     • macOS installer package is configured to disallow downgrades. Bug
       12593[3].

     • extcap: Several issues when capturing from multiple extcap
       interfaces. Bug 13653[4].

     • Expert Infos Incorrectly Displays Info Column instead of comment.
       Bug 15516[5].

     • Wireshark does not support USB packets with size greater than 256
       KiB. Bug 15985[6].

     • IS-IS: add support for decoding TE TLV Type 138 as per RFC 5307.
       Bug 16012[7].

     • NET-SNMP EngineID Length handling Warning. Bug 16051[8].

     • TLS decryption is very slow on Windows when using a large PMS
       file compared to Linux/macOS. Bug 16059[9].

     • wireshark-3.0.5/epan/dissectors/packet-nas_5gs.c:2459: bad test
       ?. Bug 16075[10].

     • ERSPAN Type III over GRE without sequence number not decoded
       correctly. Bug 16089[11].

     • Windows dumpcap -v does not display capture library info. Bug
       16108[12].

     • [Regression] FT_CHAR fields not supported in Lua API. Bug
       16129[13].

  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

   AgentX, BT L2CAP, ERSPAN, GRE, IPv4, IS-IS, NAS 5GS, OpcUa, SNMP, and
   SRT

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

  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[15] 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/[16]

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

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

 Frequently Asked Questions

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

  Last updated 2019-10-23 17:32:16 UTC

 References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6991
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11399
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12593
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13653
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15516
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15985
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16012
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16051
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16059
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16075
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16089
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16108
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16129
  14. https://www.wireshark.org/download.html
  15. https://www.wireshark.org/download.html#thirdparty
  16. https://www.wireshark.org/docs/
  17. https://ask.wireshark.org/
  18. https://www.wireshark.org/lists/
  19. https://bugs.wireshark.org/
  20. https://www.wireshark.org/faq.html


Digests

wireshark-3.0.6.tar.xz: 30846672 bytes
SHA256(wireshark-3.0.6.tar.xz)=a87f4022a0c15ddbf1730bf1acafce9e75a4e657ce9fa494ceda0324c0c3e33e
RIPEMD160(wireshark-3.0.6.tar.xz)=366cb5aa0018aeca034154976dde40ed405d5af2
SHA1(wireshark-3.0.6.tar.xz)=785ce1faa2b813a5c1b1540497fa56eb8c0eb97d

Wireshark-win64-3.0.6.exe: 59276232 bytes
SHA256(Wireshark-win64-3.0.6.exe)=6cd2b1474d5a031b85fca00538d45487144b36d8e1db1d565fd35d251ac261d0
RIPEMD160(Wireshark-win64-3.0.6.exe)=765f452efdc88e511291980398bd60e83bd06b3f
SHA1(Wireshark-win64-3.0.6.exe)=0ec54cf0d67ad5fd6583dd8d39e7d5fc68cfbae7

Wireshark-win32-3.0.6.exe: 54074488 bytes
SHA256(Wireshark-win32-3.0.6.exe)=de97cdc3cbbd8c9170cd7fe5d67ab2e09012ccb5217f27294e8c15ac3ce5e8e0
RIPEMD160(Wireshark-win32-3.0.6.exe)=edb3fe7ec21169fa9b37cc474ab1a841442bd450
SHA1(Wireshark-win32-3.0.6.exe)=c3c7c44c4dd25a7d67faeadc63830b60c7081a91

Wireshark-win64-3.0.6.msi: 47165440 bytes
SHA256(Wireshark-win64-3.0.6.msi)=174d63fb16739f03ea8484620eed030c6ea9e4d1ae4315b530603e8ba3f6ef10
RIPEMD160(Wireshark-win64-3.0.6.msi)=d96d0360c497ba930d71180ea593e32d79a476a5
SHA1(Wireshark-win64-3.0.6.msi)=880f71f3ea2d7cce9a234e1c2f559a2e736fa9c0

Wireshark-win32-3.0.6.msi: 41975808 bytes
SHA256(Wireshark-win32-3.0.6.msi)=ffad3aa929817718db35623b47409258d6d1f5bb43c576f2486fe548c8c7e380
RIPEMD160(Wireshark-win32-3.0.6.msi)=19a9ac58df6db719d4cccd00f59f6106e0afc400
SHA1(Wireshark-win32-3.0.6.msi)=298089ff7fb51753c892a7c3e3e98e7d5ad8a2f4

WiresharkPortable_3.0.6.paf.exe: 35766872 bytes
SHA256(WiresharkPortable_3.0.6.paf.exe)=587644340f16eae22d4af2ae761c06f9034c25daf7bc1570e7af0b039f0b1642
RIPEMD160(WiresharkPortable_3.0.6.paf.exe)=96fa4a2cdb2e8ebfd4cdb3e7ecc329efc9f3fe77
SHA1(WiresharkPortable_3.0.6.paf.exe)=b910b6a7d5640b6c35df21fca7ec4f7de36be692

Wireshark 3.0.6 Intel 64.dmg: 92959097 bytes
SHA256(Wireshark 3.0.6 Intel
64.dmg)=186970a1e0b610f23cb59314feaa3ce3eeb89b7c39bb5c34b4549910f1782f04
RIPEMD160(Wireshark 3.0.6 Intel
64.dmg)=5876eedf8543277dd8f4fc89cdcd85a3fb199fee
SHA1(Wireshark 3.0.6 Intel 64.dmg)=92e507f6e9ba63f88acaae56375f533068793586

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