[Gerald Combs <gerald@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 3.2.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

    • Wireshark 3.2.0 to 3.2.2 might not update automatically on macOS
      in some cases. If you’re running those versions on macOS you might
      have to update to a later version manually. Bug 16416[1]

    • The Windows installers now ship with Npcap 0.9989. They previously
      shipped with Npcap 0.9986.

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2020-07[2] The BACapp dissector could crash. Bug
       16474[3]. CVE-2020-11647[4].

   The following bugs have been fixed:

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

     • Rename profile name loses list selection. Bug 15966[6].

     • Dissector bug warning dissecting TLS Certificate Request with
       many names. Bug 16202[7].

     • Only ACKs, but no DATA frames are visible in -> TCP Stream Graph
       -> Time Sequence (tcptrace). Bug 16281[8].

     • Copy>Description does not work properly for all tree items. Bug
       16323[9].

     • Importing profiles in Windows - zip files fail and from directory
       crashes Wireshark. Bug 16410[10].

     • Packet List selection is gone when adding or removing a display
       filter. Bug 16414[11].

     • Check for updates, and auto-update, not working in 3.2.1. Bug
       16416[12].

     • f5ethtrailer: TLS trailer creates incorrect CLIENT keylog
       entries. Bug 16417[13].

     • Buildbot crash output: randpkt-2020-03-04-18423.pcap. Bug
       16424[14].

     • File open dialog shows garbled time stamps. Bug 16429[15].

     • RTCP Bye without optional reason reported as [Malformed Packet].
       Bug 16434[16].

     • [oss-fuzz] #20732: Undefined-shift in dissect_rtcp. Bug
       16445[17].

     • SOMEIP: SOME/IP-SD dissector fails to register SOME/IP ports, if
       IPv6 is being used (BUG). Bug 16448[18].

     • tshark logs: "…​could not be opened: Too many open files.". Bug
       16457[19].

     • Typo in About Wireshark > Keyboard Shortcuts > Unignore All
       Displayed. Bug 16472[20].

     • Buildbot crash output: randpkt-2020-04-02-31746.pcap. Bug
       16477[21].

     • tshark live capture finishes with a use-after-free. Bug
       16487[22].

  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

   AFS, BACapp, Bluetooth, CoAP, Diameter3GPP, F5 Ethernet trailer, GSM
   RLC MAC, ISIS, ISIS CLV, ISIS HELLO, ISIS LSP, ISIS SNP, NAS 5GS, NR
   RRC, pcap, QUIC, RPCAP, RTCP, SOME/IP-SD, TLS, and WSP

  New and Updated Capture File Support

   pcap

 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[23] 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[24] 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[25].

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

 Frequently Asked Questions

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

  Last updated 2020-04-08 22:28:36 UTC

 References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16416
   2. https://www.wireshark.org/security/wnpa-sec-2020-07
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16474
   4. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11647
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13881
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15966
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16202
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16281
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16323
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16410
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16414
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16416
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16417
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16424
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16429
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16434
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16445
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16448
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16457
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16472
  21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16477
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16487
  23. https://www.wireshark.org/download.html#thirdparty
  24. https://ask.wireshark.org/
  25. https://www.wireshark.org/lists/
  26. https://bugs.wireshark.org/
  27. https://www.wireshark.org/faq.html


Digests

wireshark-3.2.3.tar.xz: 31572052 bytes
SHA256(wireshark-3.2.3.tar.xz)=f007e4b88c86d95e33af03e057ecc03635f54466d02371bc26489eabb274faba
RIPEMD160(wireshark-3.2.3.tar.xz)=b0f8681798a5bd180eb2f23c9ae448c5041d5bf9
SHA1(wireshark-3.2.3.tar.xz)=4656856a40b294f183900ba47651b0fc8e3950fd

Wireshark-win64-3.2.3.exe: 60097344 bytes
SHA256(Wireshark-win64-3.2.3.exe)=e345963a475b79df937b41e297e8680f1f4f0cc8e8bee715fafc50834e6cc44d
RIPEMD160(Wireshark-win64-3.2.3.exe)=f3e5b67ebffdd747d93f2059f91171e0277946e3
SHA1(Wireshark-win64-3.2.3.exe)=4dffcf07f2092ef31af1f33bae124472b24dec45

Wireshark-win32-3.2.3.exe: 54794440 bytes
SHA256(Wireshark-win32-3.2.3.exe)=98fe809f13ea9a1e917b467f7cc6b9c0a32b1f5610406d764348edf4704fe326
RIPEMD160(Wireshark-win32-3.2.3.exe)=19d4305942cf09f61d1092a0d8a6723c301d132b
SHA1(Wireshark-win32-3.2.3.exe)=1612481c50e0766860203c1ea0d61762305e9746

Wireshark-win64-3.2.3.msi: 48275456 bytes
SHA256(Wireshark-win64-3.2.3.msi)=4546285ae2d94b3d776081661e9f220b9027ef044e3fe238dce02fd971a3443d
RIPEMD160(Wireshark-win64-3.2.3.msi)=d1d4dfa95514bf7200400e464c49f7a4013aa4c7
SHA1(Wireshark-win64-3.2.3.msi)=0a52170e7df96edc70bc0c643e3031ad9666ce7d

Wireshark-win32-3.2.3.msi: 42967040 bytes
SHA256(Wireshark-win32-3.2.3.msi)=433b945f5f3fff2b52574d68a6f1516b7c126f0a44de42f660e631e697679e40
RIPEMD160(Wireshark-win32-3.2.3.msi)=e3dd66e0adb7dd80f07909234b754998b31ae04b
SHA1(Wireshark-win32-3.2.3.msi)=f5e7dd2daf3d7af3b783bc815a9c5fc15cf17555

WiresharkPortable_3.2.3.paf.exe: 36567384 bytes
SHA256(WiresharkPortable_3.2.3.paf.exe)=f6fd2bde3b9a088222780e3ac6dbbdc7b17c1434d6176abe4313a5959a15ccfb
RIPEMD160(WiresharkPortable_3.2.3.paf.exe)=f8c313fd25f287f2d8e62b8a30281c9cd56a0443
SHA1(WiresharkPortable_3.2.3.paf.exe)=af4d3563bbcd1a7e02770df6a57ce1f81f99a6de

Wireshark 3.2.3 Intel 64.dmg: 97577084 bytes
SHA256(Wireshark 3.2.3 Intel 64.dmg)=066a05b20dce30f55a9ae8543cdf62771250352ab74c93186b8fb8a37a3aaf18
RIPEMD160(Wireshark 3.2.3 Intel 64.dmg)=75cd9beb21db947fd8bf53457658ac5d8da222c4
SHA1(Wireshark 3.2.3 Intel 64.dmg)=3d49e04ed0120aabac15a82956fa8fdf6369f116

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