Wireshark · Wireshark-announce: [Wireshark-announce] Wireshark 2.4.7 is now available

[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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

  Bug Fixes

   The following vulnerabilities have been fixed:
     * [1]wnpa-sec-2018-25
       The LDSS dissector could crash. ([2]Bug 14615)
     * [3]wnpa-sec-2018-28
       Multiple dissectors could consume excessive memory. ([4]Bug 14678)
     * [5]wnpa-sec-2018-29
       The DNS dissector could crash. ([6]Bug 14681)
     * [7]wnpa-sec-2018-30
       The GSM A DTAP dissector could crash. ([8]Bug 14688)
     * [9]wnpa-sec-2018-31
       The Q.931 dissector could crash. ([10]Bug 14689)
     * [11]wnpa-sec-2018-33
       Multiple dissectors could crash. ([12]Bug 14703)

   The following bugs have been fixed:
     * Double "Full Screen" menu item on macOS. ([13]Bug 13366)
     * Segmentation fault when switching profiles. ([14]Bug 14316)
     * extcap: InterfaceToolbar control pipe broken. ([15]Bug 14532)
     * SIP Response-time not being well calculated. ([16]Bug 14551)
     * HP-UX HP ANSI C requires -Wp,-H200000 flag to compile. ([17]Bug
       14554)
     * Power Capability tag interpreted incorrectly. ([18]Bug 14593)
     * Issue while building latest version of wireshark 2.4.6. ([19]Bug
       14597)
     * SMB2 Write requests not displayed. ([20]Bug 14598)
     * Wrong default file format chosen in when saving a capture with
       comments added if the original format doesn't support comments.
       ([21]Bug 14601)
     * ui/macosx directory missing from source release tarball. ([22]Bug
       14627)
     * Wireshark 2.9.0 snapshot crashes/segfaults on Windows when launched
       with -k or -i. ([23]Bug 14632)
     * File missing from release tarball. ([24]Bug 14634)
     * Remove: HACK to support UHD's weird header offset on data packets.
       ([25]Bug 14641)
     * WinSparkle 0.5.6 is out of date and is buggy. ([26]Bug 14642)
     * RTMPT: incorrect dissection of multiple RTMP packets within a
       single TCP packet. ([27]Bug 14650)
     * Erroneous MAC-LTE Dissection for Sidelink Shared Channel Packets.
       ([28]Bug 14669)
     * Files missing from docbook CMake file. ([29]Bug 14676)

  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

   BATADV, BT LE LL, BVLC, DLT_USER, DNS, GSM A BSSMAP, GSM A DTAP, GSM A
   GM, GTP, GTPv2, IEEE 802.11, LAPDm, LDSS, Logcat Text, LwM2M-TLV, MAC
   LTE, MP2T, MPEG PES, NBSS, Q.931, RSL, RTMPT, S7COMM, SIP, TCP, and
   VITA 49

  New and Updated Capture File Support

   3GPP TS 32.423 Trace, and Android Logcat
     __________________________________________________________________

Getting Wireshark

   Wireshark source code and installation packages are available from
   [30]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 [31]download page 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.
     __________________________________________________________________

Known Problems

   Dumpcap might not quit if Wireshark or TShark crashes. ([32]Bug 1419)

   The BER dissector might infinitely loop. ([33]Bug 1516)

   Capture filters aren't applied when capturing from named pipes.
   ([34]Bug 1814)

   Filtering tshark captures with read filters (-R) no longer works.
   ([35]Bug 2234)

   Application crash when changing real-time option. ([36]Bug 4035)

   Wireshark and TShark will display incorrect delta times in some cases.
   ([37]Bug 4985)

   Wireshark should let you work with multiple capture files. ([38]Bug
   10488)
     __________________________________________________________________

Getting Help

   Community support is available on [39]Wireshark's Q&A site and on the
   wireshark-users mailing list. Subscription information and archives for
   all of Wireshark's mailing lists can be found on [40]the web site.

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

Frequently Asked Questions

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

   Last updated 2018-05-21 20:14:10 UTC

References

   1. https://www.wireshark.org/security/wnpa-sec-2018-25.html
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14615
   3. https://www.wireshark.org/security/wnpa-sec-2018-28.html
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14678
   5. https://www.wireshark.org/security/wnpa-sec-2018-29.html
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14681
   7. https://www.wireshark.org/security/wnpa-sec-2018-30.html
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14688
   9. https://www.wireshark.org/security/wnpa-sec-2018-31.html
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14689
  11. https://www.wireshark.org/security/wnpa-sec-2018-33.html
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14703
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13366
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14316
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14532
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14551
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14554
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14593
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14597
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14598
  21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14601
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14627
  23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14632
  24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14634
  25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14641
  26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14642
  27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14650
  28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14669
  29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14676
  30. https://www.wireshark.org/download.html
  31. https://www.wireshark.org/download.html#thirdparty
  32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
  33. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  34. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  35. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  36. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  37. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  38. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  39. https://ask.wireshark.org/
  40. https://www.wireshark.org/lists/
  41. http://www.wiresharktraining.com/
  42. https://www.wireshark.org/faq.html


Digests

wireshark-2.4.7.tar.xz: 28938976 bytes
SHA256(wireshark-2.4.7.tar.xz)=5ecb3c68734fb89c83ac283e6cdf264eb15b9c7e7ea63dcfd4f0bad3e77c4f44
RIPEMD160(wireshark-2.4.7.tar.xz)=b9757d7944a9b7acb8b020a66b97dc0fe974ccaf
SHA1(wireshark-2.4.7.tar.xz)=8c2a56837408fd962324053ddd17692bda615499

Wireshark-win64-2.4.7.exe: 57931312 bytes
SHA256(Wireshark-win64-2.4.7.exe)=7d9d717bb64c99df8ef2a39c08d74b75d61179dc20caa7a23830f8f143c411c1
RIPEMD160(Wireshark-win64-2.4.7.exe)=6bd0be5322aa5045d422f3ff149e483022a534a2
SHA1(Wireshark-win64-2.4.7.exe)=9421b0f5244c5642d233ca30348a76c7c1989f0d

Wireshark-win32-2.4.7.exe: 52735200 bytes
SHA256(Wireshark-win32-2.4.7.exe)=f6674211588652367f4f5b66475ee470f5895064d5f90ce0756e4df2ad505c3f
RIPEMD160(Wireshark-win32-2.4.7.exe)=1bf5b935c849255191e40e99423bf028065ebae6
SHA1(Wireshark-win32-2.4.7.exe)=66ae31558cb84a30b25a505d0e62442c172a8cf0

Wireshark-win32-2.4.7.msi: 41988096 bytes
SHA256(Wireshark-win32-2.4.7.msi)=1eefd8814af949f626fa9f9b30037175a82ce7721ab24f3a1118c503693400a6
RIPEMD160(Wireshark-win32-2.4.7.msi)=a3e36cef7fa904b891c8de0b74ece74c9bf072f0
SHA1(Wireshark-win32-2.4.7.msi)=bbe011a9216a4396a9b3874bd87b09651e06b99b

Wireshark-win64-2.4.7.msi: 47054848 bytes
SHA256(Wireshark-win64-2.4.7.msi)=c00133a0840f3826e3ef8927fd89623495bb864fc24b9f7e64fcf668699e5b5e
RIPEMD160(Wireshark-win64-2.4.7.msi)=38a818c9ecef412691a6ce69b1a7d22eaead327a
SHA1(Wireshark-win64-2.4.7.msi)=2b966983fe8f9a7f596dc7cdb3ebf3ec51cfd475

WiresharkPortable_2.4.7.paf.exe: 45397560 bytes
SHA256(WiresharkPortable_2.4.7.paf.exe)=ae899f98dc111c9ec40f5e96fdfdebd3e593bba5d676707b82dee117b37a4509
RIPEMD160(WiresharkPortable_2.4.7.paf.exe)=0c75cf52637afc2d7414a1691525753a32714b97
SHA1(WiresharkPortable_2.4.7.paf.exe)=4a81e47061f8cc946d8e6e2819def71b67cde94c

Wireshark 2.4.7 Intel 64.dmg: 42526248 bytes
SHA256(Wireshark 2.4.7 Intel
64.dmg)=33667b3ae171b52bf4dc0adf13169cc73285e6a19d3562417c2f3ec3334a6740
RIPEMD160(Wireshark 2.4.7 Intel
64.dmg)=bc7f34d754bda27a31dd8fae33b2d18f3721af2b
SHA1(Wireshark 2.4.7 Intel 64.dmg)=6612bdec83558f13e90bde6ad9064ccac831f86c

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