Wireshark-announce: [Wireshark-announce] Wireshark 2.6.20 is now available
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <[email protected]>
Date: Thu, 24 Sep 2020 08:57:42 -0700
I'm proud to announce the release of Wireshark 2.6.20.


 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.6 branch. It will reach
  its official end of life on October 18, 2020. If you are still using
  Wireshark 2.6 you are encouraged to upgrade to Wireshark 3.2.

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2020-11[1] MIME Multipart dissector crash. Bug 16741[2].
       Fixed in master: 2411eae9ed Fixed in master-3.2: 21f082cb6e Fixed
       in master-3.0: 14e274f3be Fixed in master-2.6: 5803c7b87b

     • wnpa-sec-2020-12[3] TCP dissector crash. Bug 16816[4]. Fixed in
       master: c4634b1e99 Fixed in master-3.2: e9b727595b Fixed in
       master-3.0: 7f3fe6164a Fixed in master-2.6: 9d7ab8b46f

     • Buildbot crash output: fuzz-2020-07-28-5905.pcap Bug 16741[5].

   The following bugs have been fixed:

     • Buildbot crash output: randpkt-2019-04-01-28345.pcap Bug
       15661[6].

     • Buildbot crash output: fuzz-2020-07-28-5905.pcap Bug 16741[7].

     • S1-U data forwarding info and S103 PDN data forwarding info IE’s
       showing improper value Bug 16777[8].

     • Wireshark fails to detect libssh >= 0.9.5 Bug 16845[9].

  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

   AARP, BSSMAP, GSM A RR, GTPv2, MIME Multipart, NCP, Q.933, S1AP, TCP,
   and X2AP

  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.

  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[10] 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

  The BER dissector might infinitely loop. Bug 1516[11].

  Capture filters aren’t applied when capturing from named pipes. Bug
  1814[12].

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

  Application crash when changing real-time option. Bug 4035[14].

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

  Wireshark should let you work with multiple capture files. Bug
  10488[16].

 Getting Help

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

 Frequently Asked Questions

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

  Last updated 2020-09-23 21:59:44 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2020-11
   2. https://gitlab.com/wireshark/wireshark/-/issues/16741
   3. https://www.wireshark.org/security/wnpa-sec-2020-12
   4. https://gitlab.com/wireshark/wireshark/-/issues/16816
   5. https://gitlab.com/wireshark/wireshark/-/issues/16741
   6. https://gitlab.com/wireshark/wireshark/-/issues/15661
   7. https://gitlab.com/wireshark/wireshark/-/issues/16741
   8. https://gitlab.com/wireshark/wireshark/-/issues/16777
   9. https://gitlab.com/wireshark/wireshark/-/issues/16845
  10. https://www.wireshark.org/download.html#thirdparty
  11. https://gitlab.com/wireshark/wireshark/-/issues/1516
  12. https://gitlab.com/wireshark/wireshark/-/issues/1814
  13. https://gitlab.com/wireshark/wireshark/-/issues/2234
  14. https://gitlab.com/wireshark/wireshark/-/issues/4035
  15. https://gitlab.com/wireshark/wireshark/-/issues/4985
  16. https://gitlab.com/wireshark/wireshark/-/issues/10488
  17. https://ask.wireshark.org/
  18. https://www.wireshark.org/lists/
  19. https://www.wireshark.org/faq.html


Digests

wireshark-2.6.20.tar.xz: 28557592 bytes
SHA256(wireshark-2.6.20.tar.xz)=c5703cf3357d73eaa537f146a60903c0cebf5bdc8d16b6b4ae9f0310da53cfaa
RIPEMD160(wireshark-2.6.20.tar.xz)=28a27f4474fc8f5a1bb44130864e530e0153a369
SHA1(wireshark-2.6.20.tar.xz)=1f1e3a21f186aee6e5f785a6a72c67733bf69c16

Wireshark-win32-2.6.20.exe: 54121928 bytes
SHA256(Wireshark-win32-2.6.20.exe)=e278ca2729f5d6e2c1db193245cbc7ebbef84f622e5b6fb7a1ec1f97d0cf353b
RIPEMD160(Wireshark-win32-2.6.20.exe)=a459aecfb1b80f89e1c2e502de652197952b637a
SHA1(Wireshark-win32-2.6.20.exe)=392e8eadb422942f83c04e7c4cfe4e3106a53ffe

Wireshark-win64-2.6.20.exe: 59756720 bytes
SHA256(Wireshark-win64-2.6.20.exe)=8f1ea0114ca7b4aa2b00f55ea7f0f202099e56db41cacbb20e522c4a4ba2f8e7
RIPEMD160(Wireshark-win64-2.6.20.exe)=84d38f68e6f1fcbf2dc346f94cd40ce3bc1b26b3
SHA1(Wireshark-win64-2.6.20.exe)=a5ab297f872242e3313c852b1d8968744d29ea76

Wireshark-win64-2.6.20.msi: 49238016 bytes
SHA256(Wireshark-win64-2.6.20.msi)=ec540ef45ccec893b70e3244637b7e70de3f656d64f3c99ba82b3ce4178989af
RIPEMD160(Wireshark-win64-2.6.20.msi)=e43a720b2346c269944b70409e4d4f2abd923244
SHA1(Wireshark-win64-2.6.20.msi)=6c332365c511a1df1a1033faea823dba7e148026

Wireshark-win32-2.6.20.msi: 43614208 bytes
SHA256(Wireshark-win32-2.6.20.msi)=92a211dcda8002ae604835d298b0480ab14174318d6b446d804ce549ed81660b
RIPEMD160(Wireshark-win32-2.6.20.msi)=3c8f98a98f699e9ff0a41916020f7b4eb21a00e8
SHA1(Wireshark-win32-2.6.20.msi)=657ba6f1041aeb76689143bba31fe45e511f1983

WiresharkPortable_2.6.20.paf.exe: 37367584 bytes
SHA256(WiresharkPortable_2.6.20.paf.exe)=de7d8cfe7e24fbe909050b0d00935486956d04bf7f49067babef2b4e5844079d
RIPEMD160(WiresharkPortable_2.6.20.paf.exe)=4419d3bc0a9deaf0f6408c8959e42acac1f37f0c
SHA1(WiresharkPortable_2.6.20.paf.exe)=fbbcbef50f43bc3a15f9590576098aba59d834df

Wireshark 2.6.20 Intel 64.dmg: 108276233 bytes
SHA256(Wireshark 2.6.20 Intel 64.dmg)=4308825cf82f97921500c5f7f6620ce1ddd9a8a937e0960853b4f44325465c79
RIPEMD160(Wireshark 2.6.20 Intel 64.dmg)=8d586566297c39da8ce7defc55f0a81dd7648051
SHA1(Wireshark 2.6.20 Intel 64.dmg)=d57c7d733aa7b541ffb3f112960793beba6407df

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