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

[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 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:

     • wnpa-sec-2019-19[1] Wireshark dissection engine crash. Bug
       15778[2].

   The following bugs have been fixed:

     • [oss-fuzz] ERROR: Adding ospf.v3.prefix.options.nu would put more
       than 1000000 items in the tree — possible infinite loop. Bug
       14978[3].

     • Help file doesn’t display for extcap interfaces. Bug 15592[4].

     • Statistics→Conversations→TCP→Follow Stream - incorrect behavior.
       Bug 15672[5].

     • Wrong NTP timestamp for RTCP XR RR packets (hf_rtcp_xr_timestamp
       field). Bug 15687[6].

     • ws_pipe: leaks pipe handles on errors. Bug 15689[7].

     • ISAKMP: Segmentation fault with non-hex string for IKEv1
       Decryption Table Initiator Cookie. Bug 15709[8].

     • print.c: Memory leak in ek_check_protocolfilter. Bug 15758[9].

     • Bacnet(app): fix wrong value for id 183 (logging-device →
       logging-object). Bug 15767[10].

     • The SMB2 code to look up decryption keys by session ID assumes
       it’s running on a little-endian machine. Bug 15772[11].

     • tshark -G folders leaves mmdbresolve process behind. Bug
       15777[12].

  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

   BACapp, DDP, Frame, IEEE 802.11, IS-IS CLV, RTCP XR RR, and SMB2

  New and Updated Capture File Support

   pcapng

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

  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[14] 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[15].

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

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

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

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

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

 Getting Help

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

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

 Frequently Asked Questions

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

  Last updated 2019-05-21 22:50:55 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2019-19
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15778
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14978
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15592
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15672
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15687
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15689
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15709
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15758
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15767
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15772
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15777
  13. https://www.wireshark.org/download.html
  14. https://www.wireshark.org/download.html#thirdparty
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  21. https://ask.wireshark.org/
  22. https://www.wireshark.org/lists/
  23. http://www.wiresharktraining.com/
  24. https://www.wireshark.org/faq.html


Digests

wireshark-2.6.9.tar.xz: 28423640 bytes
SHA256(wireshark-2.6.9.tar.xz)=0d8c1a95a915919222f6b1a8e7fa1151a198138ab0d9327f1e93091c3b5106be
RIPEMD160(wireshark-2.6.9.tar.xz)=4355a178fd0ff671992dae87c2e3489e921b9c06
SHA1(wireshark-2.6.9.tar.xz)=0ab486a84029d1bee184f01207bb3757d4e9112f

Wireshark-win32-2.6.9.exe: 54137600 bytes
SHA256(Wireshark-win32-2.6.9.exe)=7b59968d7618f0dad22483e4992b9b024e5b0bb98a11f8ce64290509143bb626
RIPEMD160(Wireshark-win32-2.6.9.exe)=b91efd3b534f63121ee72b1e241e327ede3fadd9
SHA1(Wireshark-win32-2.6.9.exe)=c7a63ead9fe93c3253097f233c9e3163a7292632

Wireshark-win64-2.6.9.exe: 59775848 bytes
SHA256(Wireshark-win64-2.6.9.exe)=943eb06f2652720ae177729dbe887f11d79ca3232a6e6f4c6c2e0a1863ec7228
RIPEMD160(Wireshark-win64-2.6.9.exe)=16c7c96076e313dd95e971236426b7b10e8262b4
SHA1(Wireshark-win64-2.6.9.exe)=4f6e29c2a1bc64904a79a2219a8210f6fbc4f173

Wireshark-win32-2.6.9.msi: 43614208 bytes
SHA256(Wireshark-win32-2.6.9.msi)=108e7edaee7b7ad2f99dc028cc37498969b7a6c9457f06479d72725363a93171
RIPEMD160(Wireshark-win32-2.6.9.msi)=cefc5913f7d5e6e2db3f50ddf65171719ede32e9
SHA1(Wireshark-win32-2.6.9.msi)=a252b86e3badadbdef84b82d3a9d7686054f120d

Wireshark-win64-2.6.9.msi: 49238016 bytes
SHA256(Wireshark-win64-2.6.9.msi)=fb6fa93ceec87be7e991ee682e5e7082e525a8ae5e1c89e7406596c45dace811
RIPEMD160(Wireshark-win64-2.6.9.msi)=4b3287b822edef1d817cde031f68109fc1bff034
SHA1(Wireshark-win64-2.6.9.msi)=c4561eb63b83f274a5abac88431fd29dd7c62116

WiresharkPortable_2.6.9.paf.exe: 37346880 bytes
SHA256(WiresharkPortable_2.6.9.paf.exe)=8efe0f1c9a409d91e6dab5b56aadf08068086b135fad6f98656e55e6d37b3edb
RIPEMD160(WiresharkPortable_2.6.9.paf.exe)=882fdad20652902c603f06c54a297ed01ea222ce
SHA1(WiresharkPortable_2.6.9.paf.exe)=ccc32b3cd67fc76a957afd42a5abccdee822a865

Wireshark 2.6.9 Intel 64.dmg: 108173778 bytes
SHA256(Wireshark 2.6.9 Intel
64.dmg)=553d333b868ac78fdff083b64f37960b577557d440eba688759db70b9bf3d43b
RIPEMD160(Wireshark 2.6.9 Intel
64.dmg)=88c285d8252ac9b4e1edb631246b9555a245630b
SHA1(Wireshark 2.6.9 Intel 64.dmg)=3890948d29a0bac25d7c4dce2ff5beeab059d2a3

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