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

[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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


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

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

    • The macOS installer now ships with Qt 5.12.4. It previously
      shipped with Qt 5.12.1.

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2019-20[1] ASN.1 BER and related dissectors crash. Bug
       15870[2]. CVE-2019-13619[3].

   The following bugs have been fixed:

     • "ninja install" installs help/faq.py instead of help/faq.txt. Bug
       15543[4].

     • In Wireshark 3.0, encrypted DOCSIS PDU packets no longer match
       the filter "eth.dst". Bug 15731[5].

     • Developer’s Guide section 3.9 "Contribute your changes" should
       incorporate or link "Writing a good commit message" from the
       Wiki. Bug 15752[6].

     • RSL dissector bugs in presence of optional IEs. Bug 15789[7].

     • The "Media Attribute Value" field is missed in rtcp SDP
       dissection (packet-sdp.c). Bug 15791[8].

     • BTLE doesn’t properly detect start fragment of L2CAP PDUs. Bug
       15807[9].

     • Wi-SUN FAN decoder error, Channel Spacing and Reserved fields are
       swapped. Bug 15821[10].

     • tshark: Display filter error message references "-d" when it
       should reference "-Y". Bug 15825[11].

     • Open "protocol" preferences …​ does not work for protocol in
       subtree. Bug 15836[12].

     • Problems with sshdump "Error by extcap pipe: sh: sudo: command
       not found". Bug 15845[13].

     • editcap won’t change encapsulation type when writing pcap format.
       Bug 15873[14].

     • ITU-T G.8113.1 MPLS-TP OAM CC,LMM,LMR,DMM and DMR are not seen in
       the 3.0.2. Bug 15887[15].

  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, ASN.1, BTLE, CUPS, DNS, DOCSIS, DPNSS, GSM RLC/MAC, HiQnet,
   ISO 14443, ISObus VT, LDAP, MAC LTE, MIME multipart, MPLS, MQ, RSL,
   SDP, SMB, TNEF, and Wi-SUN

  New and Updated Capture File Support

   Ascend

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

  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[17] 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/[18]

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

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

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

 Frequently Asked Questions

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

  Last updated 2019-07-17 17:31:51 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2019-20
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15870
   3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13619
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15543
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15731
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15752
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15789
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15791
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15807
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15821
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15825
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15836
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15845
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15873
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15887
  16. https://www.wireshark.org/download.html
  17. https://www.wireshark.org/download.html#thirdparty
  18. https://www.wireshark.org/docs/
  19. https://ask.wireshark.org/
  20. https://www.wireshark.org/lists/
  21. https://bugs.wireshark.org/
  22. http://www.wiresharktraining.com/
  23. https://www.wireshark.org/faq.html


Digests

wireshark-3.0.3.tar.xz: 30923980 bytes
SHA256(wireshark-3.0.3.tar.xz)=af92729c781d870110885c31ebcbe4c4224ed51bb580d00c896fe9746994211c
RIPEMD160(wireshark-3.0.3.tar.xz)=4ccaf1702977f7ffb225896f90807a35dd6e33cc
SHA1(wireshark-3.0.3.tar.xz)=3a7406d54de9fd925a3d9800471610144fe44354

Wireshark-win64-3.0.3.exe: 59321664 bytes
SHA256(Wireshark-win64-3.0.3.exe)=824cbeeb48ed720a24b70725cb8db2353ed331e05f3d0a832ff96acb02292d62
RIPEMD160(Wireshark-win64-3.0.3.exe)=6f8c4dad7006958441d824098a2d5475be421533
SHA1(Wireshark-win64-3.0.3.exe)=9e5f39adaa22e4016d0cba93a6e9f302d91cc313

Wireshark-win32-3.0.3.exe: 54140848 bytes
SHA256(Wireshark-win32-3.0.3.exe)=9e276aff3164e98293d478758542855bdfb7ffd295156f4d5011ba76a9cbf814
RIPEMD160(Wireshark-win32-3.0.3.exe)=c30b2818d3f5478dd0175ec739b6bb3d0c6679b0
SHA1(Wireshark-win32-3.0.3.exe)=b0fd5c543421844a8a33fa00d0594dddc5572045

Wireshark-win32-3.0.3.msi: 42061824 bytes
SHA256(Wireshark-win32-3.0.3.msi)=d220bb9459dd9dcd2eb572a112a57069d7fbe18979352a8047493bd22e9dda7b
RIPEMD160(Wireshark-win32-3.0.3.msi)=537efd1483dfcae936832017aa288e79f2f04d29
SHA1(Wireshark-win32-3.0.3.msi)=1f81dfafc3481a32f8f15f4c3f6c39f831f6e4b3

Wireshark-win64-3.0.3.msi: 47251456 bytes
SHA256(Wireshark-win64-3.0.3.msi)=9ede8409906f4830f8d9c442fd884989eac4cfc942080c73ad7b4e272c00d081
RIPEMD160(Wireshark-win64-3.0.3.msi)=e160af727a48c360011ce03de061041dc1e65826
SHA1(Wireshark-win64-3.0.3.msi)=56e258f093d4455cedc82b6d93201ea478a748f2

WiresharkPortable_3.0.3.paf.exe: 35834584 bytes
SHA256(WiresharkPortable_3.0.3.paf.exe)=f1c9ceed2eacf23bc842611ab1b11280ea850bdbc4211ec5b8de6ddce5615dd9
RIPEMD160(WiresharkPortable_3.0.3.paf.exe)=3d86c378b0994e9de4f777c45a082355107594d8
SHA1(WiresharkPortable_3.0.3.paf.exe)=f15116f2e179acc6ce40669ca478477525e1c14a

Wireshark 3.0.3 Intel 64.dmg: 93069527 bytes
SHA256(Wireshark 3.0.3 Intel
64.dmg)=71d0196e7368715958598c8286f5219eb24fad08acf1cfe9186ef19d29e04ae9
RIPEMD160(Wireshark 3.0.3 Intel
64.dmg)=1cfe89e437765afe0843cea54d670401fe0d5831
SHA1(Wireshark 3.0.3 Intel 64.dmg)=78490223d3894cd90369aaab430ba4b66d42eba5

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