Wireshark-announce: [Wireshark-announce] Wireshark 2.6.17 is now available
Date Prev · Date Next · Thread Prev · Thread Next
From: Wireshark announcements <[email protected]>
Date: Tue, 19 May 2020 13:18:05 -0700
I'm proud to announce the release of Wireshark 2.6.17.


 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

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

   The following bugs have been fixed:

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

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

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

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

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

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

     • Buildbot crash output: fuzz-2020-05-13-12195.pcap. Bug 16564[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

   AoE, APRS, ASN.1 BER, FTP, GSM SMS, Infiniband, ISObus VT, MAC LTE,
   NFS, ONC RPC, OSC, pcapng, PDCP LTE, RADIUS, RLC LTE, SDP, SIP,
   Snort, and STUN

  New and Updated Capture File Support

   Camins, Catapult DCT 2000, Lanalyzer, and MPEG

  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-05-19 18:38:34 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=16335
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16440
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16458
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16459
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16519
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16526
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16564
  10. https://www.wireshark.org/download.html#thirdparty
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  17. https://ask.wireshark.org/
  18. https://www.wireshark.org/lists/
  19. https://www.wireshark.org/faq.html


Digests

wireshark-2.6.17.tar.xz: 28523700 bytes
SHA256(wireshark-2.6.17.tar.xz)=eb37fa54f35ca56fa3532d4cf391c0600e1d068f6c1503918024c553d8067eff
RIPEMD160(wireshark-2.6.17.tar.xz)=62e7d2bf5d76a13a22cd60dff7246b1989ac9e5d
SHA1(wireshark-2.6.17.tar.xz)=8bdf29a621b848a9d3ce368855077625cc01752e

Wireshark-win64-2.6.17.exe: 59709416 bytes
SHA256(Wireshark-win64-2.6.17.exe)=ede67647da0b1c103e9ce192dd91927c9931c0b277db812324166585e18fd09a
RIPEMD160(Wireshark-win64-2.6.17.exe)=42eace40cf314896b8535e5085d9b7171ab75ffb
SHA1(Wireshark-win64-2.6.17.exe)=2c3b66ace5bfd1c0e741940d9b3abafe5f967663

Wireshark-win32-2.6.17.exe: 54072136 bytes
SHA256(Wireshark-win32-2.6.17.exe)=b72fb88ecf385e23fdb028dcc66c623d5eeff03fc226b9735907355e44194d21
RIPEMD160(Wireshark-win32-2.6.17.exe)=a0f2905242f5f7afa8e951ae00ab50442dd16280
SHA1(Wireshark-win32-2.6.17.exe)=a9dedf08861fa5431745a30bbca25c4012c32ff2

Wireshark-win64-2.6.17.msi: 49172480 bytes
SHA256(Wireshark-win64-2.6.17.msi)=508b7b5372e8b086bebd628ffbe9be7525881515ebdb8b5e3fd8e956065517b8
RIPEMD160(Wireshark-win64-2.6.17.msi)=7dcc2def1739adcbede2fb4c0e72221eafbd73df
SHA1(Wireshark-win64-2.6.17.msi)=8e04d1e4b03a6ee102619af7be809f2fa35464f7

Wireshark-win32-2.6.17.msi: 43577344 bytes
SHA256(Wireshark-win32-2.6.17.msi)=bd4243fcb9becea3f05c71641cfc314718d59b3c96de4ca60f326b7b3198f00e
RIPEMD160(Wireshark-win32-2.6.17.msi)=916ebbfc94abd46a311f534035d62db63683878e
SHA1(Wireshark-win32-2.6.17.msi)=857f09180a299a9f18ff68ae24f0dbf758bdcd4e

WiresharkPortable_2.6.17.paf.exe: 37312512 bytes
SHA256(WiresharkPortable_2.6.17.paf.exe)=b8e2c12e43511f2febcdadf195ac5cb2c907f4b864b2824cec1884d40931006a
RIPEMD160(WiresharkPortable_2.6.17.paf.exe)=a0daced4dd3baad3f760cbcafcd52ddd803ff2f6
SHA1(WiresharkPortable_2.6.17.paf.exe)=8c735ab2e7128124f8138cf0860fc18b74977036

Wireshark 2.6.17 Intel 64.dmg: 108245045 bytes
SHA256(Wireshark 2.6.17 Intel 64.dmg)=b4d428a54b0acd1f7231f581ee5ae7c7556d160b417f4996a432933a66edc92c
RIPEMD160(Wireshark 2.6.17 Intel 64.dmg)=fd9c2d420dce19a0bbffbc4bb40483145f7c0f11
SHA1(Wireshark 2.6.17 Intel 64.dmg)=8ba48729abef0515e60582093bd7a75fdf8504a5

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