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

[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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


 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 and macOS installers now ship with Qt 5.12.6. They
  previously shipped with Qt 5.12.5.

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2019-22[1] CMS dissector crash. Bug 15961[2].
       CVE-2019-19553[3].

   The following bugs have been fixed:

     • ws_pipe_wait_for_pipe() can wait on closed handles. Bug 15696[4].

     • Support for 11ax in PEEKREMOTE. Bug 15740[5].

     • The temporary file …​ could not be opened: Invalid argument. Bug
       15751[6].

     • Reassembling of the two TLS records is not working correctly. Bug
       16109[7].

     • Display Filter Area: Dropdown Missing pkt_comment and
       tcp.options.sack_perm (likely others). Bug 16130[8].

     • Display Filter autocompletion should be disabled. Bug 16132[9].

     • BGP Linkstate IP Reachability information is incorrect. Bug
       16144[10].

     • NGAP: ExpectedUEActivityBehaviour decode error. Bug 16145[11].

     • HomePlug AV dissector: MMTYPE and FMI fields are dissected
       incorrectly. Bug 16158[12].

     • JPEG files cannot be saved on Windows with french language. Bug
       16165[13].

     • X11 --display interpreted as --display-filter which maps to -Y
       option. Bug 16167[14].

     • "Create new file automatically after" not working with extcap.
       Bug 16178[15].

     • Encrypted TLS alerts sometimes listed as decrypted. Bug
       16180[16].

     • The "Remove Wireshark from the system path" package has "Add
       Wireshark to the system PATH" as its title. Bug 16200[17].

     • tshark -T ek -x causes get_field_data: code should not be
       reached. Bug 16218[18].

     • Crash on Go → Next/Previous Packet in Conversation when no packet
       is selected. Bug 16228[19].

  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

   BGP, HomePlug AV, IEEE 802.11, and TLS

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

  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[21] 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/[22]

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

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

 Frequently Asked Questions

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

  Last updated 2019-12-04 18:36:46 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2019-22
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15961
   3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19553
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15696
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15740
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15751
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16109
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16130
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16132
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16144
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16145
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16158
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16165
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16167
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16178
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16180
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16200
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16218
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16228
  20. https://www.wireshark.org/download.html
  21. https://www.wireshark.org/download.html#thirdparty
  22. https://www.wireshark.org/docs/
  23. https://ask.wireshark.org/
  24. https://www.wireshark.org/lists/
  25. https://bugs.wireshark.org/
  26. https://www.wireshark.org/faq.html


Digests

wireshark-3.0.7.tar.xz: 30851928 bytes
SHA256(wireshark-3.0.7.tar.xz)=3b2b279017753398b8d5deb440db5f98a205eea35f9417e5fa2893947e7992f2
RIPEMD160(wireshark-3.0.7.tar.xz)=7168f7bf9f724e9ec3236c998c54368d85820718
SHA1(wireshark-3.0.7.tar.xz)=c870ef818952a741773fc1143fba2834c76a1dd0

Wireshark-win64-3.0.7.exe: 59286520 bytes
SHA256(Wireshark-win64-3.0.7.exe)=b246db3ef635c5bf2ae25684f5f869c0d958c66021a5388a3fb1a38aa374b233
RIPEMD160(Wireshark-win64-3.0.7.exe)=a7d8d760941560fc48b17ec533101ae6152c9774
SHA1(Wireshark-win64-3.0.7.exe)=a431c290a226c488511072e80bb54bf0bedc19e1

Wireshark-win32-3.0.7.exe: 54086080 bytes
SHA256(Wireshark-win32-3.0.7.exe)=638141dadcc14ff14738aacc795439ef347e515cc7eb40d0624d5ecdf04c9a71
RIPEMD160(Wireshark-win32-3.0.7.exe)=0c6e84ad9c2fe0f35fd1b74ec5729e78dd76bddf
SHA1(Wireshark-win32-3.0.7.exe)=dc3b556eba870c9f45cc7fac860287692294f188

Wireshark-win32-3.0.7.msi: 42012672 bytes
SHA256(Wireshark-win32-3.0.7.msi)=4546848296541ca0e37d1f1266e18cd8607ee37867a20f16e7945a25bc8fc662
RIPEMD160(Wireshark-win32-3.0.7.msi)=ee595a35f08aa5b39df3d3311fd02e39e86036ee
SHA1(Wireshark-win32-3.0.7.msi)=47ef5b7ab802b6afb09c57eb56b70f3d26f9fded

Wireshark-win64-3.0.7.msi: 47202304 bytes
SHA256(Wireshark-win64-3.0.7.msi)=69fb3017e58587cd902a022f0b1559f843df18ffb6f242d2550b57ec46903c8f
RIPEMD160(Wireshark-win64-3.0.7.msi)=64cae654b67ad7acb942d13dd50fde33cb8a6257
SHA1(Wireshark-win64-3.0.7.msi)=fd7d4d7bb6f1db6c94d469aea7827a88638b06c5

WiresharkPortable_3.0.7.paf.exe: 35788064 bytes
SHA256(WiresharkPortable_3.0.7.paf.exe)=25863fe788dcb30e9720d08d87c40dd8748afae7a4de71fe742d99ddcc9e56a8
RIPEMD160(WiresharkPortable_3.0.7.paf.exe)=5b60e2a4dbeb9bdf2bd6b362a3b866932471fba1
SHA1(WiresharkPortable_3.0.7.paf.exe)=da667f0b7ceb181f4b8d38af5b6bfbf593d5fea0

Wireshark 3.0.7 Intel 64.dmg: 92994525 bytes
SHA256(Wireshark 3.0.7 Intel
64.dmg)=cb69a2899b5a020fbe7b844388922aa893be1580a27c6747341e6008cb1b4441
RIPEMD160(Wireshark 3.0.7 Intel
64.dmg)=2acc86a13e830067484a6aa7c53b2a5c4739e4d0
SHA1(Wireshark 3.0.7 Intel 64.dmg)=2a2dcda6ec325f181138e6e4c2222086a4a7fa61

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