Wireshark-announce: [Wireshark-announce] Wireshark 2.4.16 is now available
From: Wireshark announcements <[email protected]>
Date: Wed, 17 Jul 2019 12:02:08 -0700
I'm proud to announce the release of Wireshark 2.4.16.

     __________________________________________________________________

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

   This is the final release of the Wireshark 2.4 branch. It will reach
   its official end of life on July 19, 2019. If you are still using
   Wireshark 2.4 you are encouraged to upgrade to Wireshark 3.0.

  Bug Fixes

   The following vulnerabilities have been fixed:
     * [1]wnpa-sec-2019-20 ASN.1 BER and related dissectors crash. [2]Bug
       15870. [3]CVE-2019-13619.

   The following bugs have been fixed:
     * BTLE doesn't properly detect start fragment of L2CAP PDUs. [4]Bug
       15807.
     * Problems with sshdump "Error by extcap pipe: sh: sudo: command not
       found". [5]Bug 15845.
     * editcap won't change encapsulation type when writing pcap format.
       [6]Bug 15873.

  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

   ASN.1, BTLE, CUPS, DNS, DPNSS, GSM RLC/MAC, HiQnet, MAC LTE, MIME
   multipart, MQ, SMB, and TNEF

  New and Updated Capture File Support

   Ascend, and pcapng

  New and Updated Capture Interfaces support

   There are no new or updated capture interfaces supported in this
   release.
     __________________________________________________________________

Getting Wireshark

   Wireshark source code and installation packages are available from
   [7]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 [8]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. ([9]Bug 1419)

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

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

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

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

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

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

Getting Help

   Community support is available on [16]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 [17]the web site.

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

Frequently Asked Questions

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

   Last updated 2019-07-17 17:44:21 UTC

References

   1. https://www.wireshark.org/security/wnpa-sec-2019-20.html
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15870
   3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13619
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15807
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15845
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15873
   7. https://www.wireshark.org/download.html
   8. https://www.wireshark.org/download.html#thirdparty
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  16. https://ask.wireshark.org/
  17. https://www.wireshark.org/lists/
  18. http://www.wiresharktraining.com/
  19. https://www.wireshark.org/faq.html


Digests

wireshark-2.4.16.tar.xz: 29205200 bytes
SHA256(wireshark-2.4.16.tar.xz)=a6a807c5985a909155763e9533d72a03c59b062824b21a2afd867ca1d2f72239
RIPEMD160(wireshark-2.4.16.tar.xz)=ecff42d7945e2012ae1a76cd790684241a63b0f4
SHA1(wireshark-2.4.16.tar.xz)=b7a3625412e8ce1d93a2b748ffe4863a1b741fb8

Wireshark-win64-2.4.16.exe: 58094800 bytes
SHA256(Wireshark-win64-2.4.16.exe)=f18a41dd05fb06e49f5cc389e8649634f9efb3a53afeb4a4d25f1be682cfe407
RIPEMD160(Wireshark-win64-2.4.16.exe)=f5b1827e56ee876a2abcde707b98c303a89f52bf
SHA1(Wireshark-win64-2.4.16.exe)=4230ab636b977d5d4b804436bd84882358aa5700

Wireshark-win32-2.4.16.exe: 52877704 bytes
SHA256(Wireshark-win32-2.4.16.exe)=667d7d944780154482aa6a5695f9f7f84dc40ae65734dd097cad86a5c2a6ba4d
RIPEMD160(Wireshark-win32-2.4.16.exe)=c73721122ef5997a025916ffe1488a4f842d22ba
SHA1(Wireshark-win32-2.4.16.exe)=80abebd4fc77cc47480a95dd5b8e9ac78a16c6a5

Wireshark-win32-2.4.16.msi: 42139648 bytes
SHA256(Wireshark-win32-2.4.16.msi)=12638e60da8e52fc3502198c6edc150736ee11a490788df601093476f17daf21
RIPEMD160(Wireshark-win32-2.4.16.msi)=2bbf52bb4ca1f06d2f00b76fb4e55eb1420abae2
SHA1(Wireshark-win32-2.4.16.msi)=3d96c42a346d250ac50d57d7d1a2efa9cca69169

Wireshark-win64-2.4.16.msi: 47190016 bytes
SHA256(Wireshark-win64-2.4.16.msi)=a8612fa6fe90c69289cf622db34af9d9723b504f4d7dff9e28a89b0c64e770b7
RIPEMD160(Wireshark-win64-2.4.16.msi)=52f0ed32727f915181e8d5356b68f40e1ed3b3c0
SHA1(Wireshark-win64-2.4.16.msi)=dfffd23339da094c9af7466bc4634314ceea5bb4

WiresharkPortable_2.4.16.paf.exe: 45510240 bytes
SHA256(WiresharkPortable_2.4.16.paf.exe)=172e7624189c2ae79c03bdacfebbbfabc5a1fa3f07237841bfb7bde173d9002b
RIPEMD160(WiresharkPortable_2.4.16.paf.exe)=653542fe34529007e05a62f6ed3d7fa48b84797f
SHA1(WiresharkPortable_2.4.16.paf.exe)=edf279f49bc1a1f61bf08e837b0ae76cd6ca4d3e

Wireshark 2.4.16 Intel 64.dmg: 42618219 bytes
SHA256(Wireshark 2.4.16 Intel
64.dmg)=7b37b04b7430b43ab37fd40daf63d4c1f6cd0e646c1b902525c3bc06e63dc8e0
RIPEMD160(Wireshark 2.4.16 Intel
64.dmg)=4098e1f67117ff5af0a929b06bbb2f88da68c5d9
SHA1(Wireshark 2.4.16 Intel 64.dmg)=04418f9cf1ff1421d859369f284d71c82f28a941

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