[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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


 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.8. They previously
  shipped with Qt 5.12.6.

  The Windows installers now ship with Npcap 0.9991 They previously
  shipped with Npcap 0.9989

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2020-08[1] The NFS dissector could crash. Bug 16476[2].

   The following bugs have been fixed:

     • SDP dissector does not parse sprop-parameter-sets field. Bug
       16322[3].

     • PVS-Studio analyser long list of issues. Bug 16335[4].

     • Can’t have duplicate personal and global profile names. Bug
       16423[5].

     • pcapng file dissector incorrectly computes nanoseconds from
       timestamps because it assumes the resolution is in nanoseconds.
       Bug 16440[6].

     • Read of uninitialized memory in detect_camins_file. Bug 16458[7].

     • Read of uninitialized memory in lanalyzer_read_trace_record. Bug
       16459[8].

     • capture -> options -> select interface -> (choose) -> SEGV. Bug
       16489[9].

     • SOMEIP: SOME/IP dissector ignores the length field configuration
       of structs. Bug 16490[10].

     • Packet List Pane doesn’t consume the entire pane. Bug 16491[11].

     • Range parameter on numeric parameter in extcap plugin doesn’t
       work. Bug 16510[12].

     • Export Packet Dissections not working on Windows (Wireshark
       3.2.x). Bug 16516[13].

     • capinfos "Capture duration" output is truncated if there are more
       than 11 digits of seconds and fractions of a second. Bug
       16519[14].

     • MIME Files Format/pcapng: Simple Packet Block parsed incorrectly.
       Bug 16526[15].

     • SOMEIP: SOME/IP-SD unique id is not unique for eventgroup types
       (BUG). Bug 16549[16].

     • Buildbot crash output: fuzz-2020-05-13-12195.pcap. Bug 16564[17].

  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

   AoE, APRS, ASN.1 BER, DIS, DTLS, FTP, GSM SMS, H.264, IMAP,
   Infiniband, ISObus VT, Kafka, LSD, MAC LTE, NAS 5GS, NFS, ONC RPC,
   OSC, pcapng, PDCP LTE, RADIUS, RLC LTE, RTSP, SDP, SIP, Snort,
   SOMEIP, STUN, TLS, and UMTS FP

  New and Updated Capture File Support

   Camins, Catapult DCT 2000, Lanalyzer, and MPEG

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

 Frequently Asked Questions

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

  Last updated 2020-05-19 17:45:44 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2020-08
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16476
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16322
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16335
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16423
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16440
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16458
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16459
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16489
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16490
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16491
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16510
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16516
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16519
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16526
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16549
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16564
  18. https://www.wireshark.org/download.html#thirdparty
  19. https://ask.wireshark.org/
  20. https://www.wireshark.org/lists/
  21. https://bugs.wireshark.org/
  22. https://www.wireshark.org/faq.html


Digests

wireshark-3.2.4.tar.xz: 31580440 bytes
SHA256(wireshark-3.2.4.tar.xz)=d17d461e849e2d0b033431c45f71d8ee8ec3c8faa232a6ad63069a47927db8aa
RIPEMD160(wireshark-3.2.4.tar.xz)=5dccf5ba44dd8f6c275b74ab07137ce80f4ab76d
SHA1(wireshark-3.2.4.tar.xz)=bb4157b57c1bcdbac948a1282dafad027d57be9b

Wireshark-win32-3.2.4.exe: 54867824 bytes
SHA256(Wireshark-win32-3.2.4.exe)=c17e4a812031d5dfd4ef0a4b4dae1b60bb45eb7ce8c9e8b1b5eff4db5bcf4b72
RIPEMD160(Wireshark-win32-3.2.4.exe)=3ac743c96a4b1e9e006501e45b1a8f398d54d511
SHA1(Wireshark-win32-3.2.4.exe)=ea4cc781339618eb16db4fdc96c413f119229ef3

Wireshark-win64-3.2.4.exe: 60037848 bytes
SHA256(Wireshark-win64-3.2.4.exe)=db2565ee6410b7c57f54aaac86954e4f6a98e2ea31ffbea83e60b981fff57301
RIPEMD160(Wireshark-win64-3.2.4.exe)=e058bfdb62c1b0392d39c80d24e7f001587ed907
SHA1(Wireshark-win64-3.2.4.exe)=32c0cea3623db22eb7f0dbf24ac4902a4e873f3d

Wireshark-win32-3.2.4.msi: 43028480 bytes
SHA256(Wireshark-win32-3.2.4.msi)=a614bdb63e9dfa1150cdcb471790ebe32f1c8a269079cbccab6ece4ad7700575
RIPEMD160(Wireshark-win32-3.2.4.msi)=7431e01c63b522ad59f1adb58fa0da7e5b12362b
SHA1(Wireshark-win32-3.2.4.msi)=22ca61d51e9d66e198769225fbbc0bfc2f3a0f76

Wireshark-win64-3.2.4.msi: 48283648 bytes
SHA256(Wireshark-win64-3.2.4.msi)=eb13bc841c98c398a7f26705f3621ac4ffe90fc158f4ea48db3ba56968a0d41b
RIPEMD160(Wireshark-win64-3.2.4.msi)=33e2f498e1919a11b1c20cb125af30c304534cc8
SHA1(Wireshark-win64-3.2.4.msi)=4e2aeab60879518b5d9a81d8449874db23ad4dc6

WiresharkPortable_3.2.4.paf.exe: 36581616 bytes
SHA256(WiresharkPortable_3.2.4.paf.exe)=2c8ea4e6776a334d43909c53d7c656db10ad425beec5fe927b8d1fb0467309da
RIPEMD160(WiresharkPortable_3.2.4.paf.exe)=759413437b7b91efe28eab3c6120530421ada774
SHA1(WiresharkPortable_3.2.4.paf.exe)=6c0f29f5554b0ee7160b21f7a6c6a5069161e266

Wireshark 3.2.4 Intel 64.dmg: 97572886 bytes
SHA256(Wireshark 3.2.4 Intel 64.dmg)=735d43bdbde1caeb9bfff89acc62acfeb05ffda36e6d0d243bc08333e60fdac6
RIPEMD160(Wireshark 3.2.4 Intel 64.dmg)=672b26161f45f015fff6d16d96570b85f59c0bcb
SHA1(Wireshark 3.2.4 Intel 64.dmg)=5a550cae3e5cc02441f39df2fdb84edb525d5b87

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