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


 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-20[1] ASN.1 BER and related dissectors crash. Bug
       15870[2]. CVE-2019-13619[3].

   The following bugs have been fixed:

     • Wireshark 2.6.3 crashes in QIcon destructor on closing the main
       window on Ubuntu 14.04 and 16.04. Bug 15241[4].

     • RSL dissector bugs in presence of optional IEs. Bug 15789[5].

     • The "Media Attribute Value" field is missed in rtcp SDP
       dissection (packet-sdp.c). Bug 15791[6].

     • BTLE doesn’t properly detect start fragment of L2CAP PDUs. Bug
       15807[7].

     • tshark: Display filter error message references "-d" when it
       should reference "-Y". Bug 15825[8].

     • Open "protocol" preferences …​ does not work for protocol in
       subtree. Bug 15836[9].

     • Problems with sshdump "Error by extcap pipe: sh: sudo: command
       not found". Bug 15845[10].

     • editcap won’t change encapsulation type when writing pcap format.
       Bug 15873[11].

  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, ISObus VT, MAC
   LTE, MIME multipart, MQ, RSL, SDP, SMB, and TNEF

  New and Updated Capture File Support

   Ascend

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

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

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

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

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

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

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

 Getting Help

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

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

 Frequently Asked Questions

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

  Last updated 2019-07-17 17:39:04 UTC

 References

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


Digests

wireshark-2.6.10.tar.xz: 28436884 bytes
SHA256(wireshark-2.6.10.tar.xz)=b8fc32244352437db727a4517371dddfa9ffbf0057cfb58265588876b42b6c7e
RIPEMD160(wireshark-2.6.10.tar.xz)=b7531d10b0a15cb3e61f16047476e24c504ea7d1
SHA1(wireshark-2.6.10.tar.xz)=942825e0fc65502fac11886f35afffdc20fdaca0

Wireshark-win32-2.6.10.exe: 54145072 bytes
SHA256(Wireshark-win32-2.6.10.exe)=7f609dc1b226492f32413bff241549a3234f59a30fb6dc324931be5fca3b3b3f
RIPEMD160(Wireshark-win32-2.6.10.exe)=52ee241d9eab506ae5889882f41109926d30b60c
SHA1(Wireshark-win32-2.6.10.exe)=02f0212ca7fde1a3935daa34e7df0b31aed932b3

Wireshark-win64-2.6.10.exe: 59783744 bytes
SHA256(Wireshark-win64-2.6.10.exe)=1865445a9531c314796e0f6672f1649fb2c56f67f86482a00958d7a9f165c224
RIPEMD160(Wireshark-win64-2.6.10.exe)=deea54900954cd4d136de530d48b89fac7e5204c
SHA1(Wireshark-win64-2.6.10.exe)=5b489a949ff1a2feea1d37e14bf35a54e215d7de

Wireshark-win64-2.6.10.msi: 49242112 bytes
SHA256(Wireshark-win64-2.6.10.msi)=7c14d253dce52a9eb2e4bb2e1b90ab1f5dddb709fe7b525aacc2549c1d3c5c73
RIPEMD160(Wireshark-win64-2.6.10.msi)=1c20e20122280f2c3d4ac0067efffee221e51fc3
SHA1(Wireshark-win64-2.6.10.msi)=21ae45e84eca8422683000775b2be0490c9ea710

Wireshark-win32-2.6.10.msi: 43638784 bytes
SHA256(Wireshark-win32-2.6.10.msi)=fd16e33976e1f0f91a5aed5c5cc07dd6397b8b47387443c858a9ab84a170e44b
RIPEMD160(Wireshark-win32-2.6.10.msi)=94d56d74bcb4a5f26142b72c51f0e6fa65dceaf7
SHA1(Wireshark-win32-2.6.10.msi)=d613d375484f1f245bc770a361709c0fea72884b

WiresharkPortable_2.6.10.paf.exe: 37349080 bytes
SHA256(WiresharkPortable_2.6.10.paf.exe)=82ca82dbba8e826ef9d586d4c87dcbb0973925d1454496d2de85a70164d2a6d1
RIPEMD160(WiresharkPortable_2.6.10.paf.exe)=0510597ed2ae289971963f0ddf5467b008b4a666
SHA1(WiresharkPortable_2.6.10.paf.exe)=4ce551c254ac30515bf6916fb88189d0bb0f599f

Wireshark 2.6.10 Intel 64.dmg: 108186987 bytes
SHA256(Wireshark 2.6.10 Intel
64.dmg)=afc19da6bd2073b4977c442f4cf26e6ab63b164dd9353ca9b4c0e01bd303da09
RIPEMD160(Wireshark 2.6.10 Intel
64.dmg)=d2d0cc771bdb5a8e204e73b8177b2404583003af
SHA1(Wireshark 2.6.10 Intel 64.dmg)=4af6253b906855f00866494c814102528cbc3ea9

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