Wireshark-dev: [Wireshark-dev] Wireshark 2.6.6 is now available
From: Gerald Combs <[email protected]>
Date: Tue, 8 Jan 2019 13:27:05 -0800
I'm proud to announce the release of Wireshark 2.6.6.


 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

    • The Windows installers now ship with Qt 5.9.7. Previously they
      shipped with Qt 5.9.5.

  Bug Fixes

   The following vulnerabilities have been fixed:

     • wnpa-sec-2019-01[1] The 6LoWPAN dissector could crash. Bug
       15217[2]. CVE-2019-5716[3].

     • wnpa-sec-2019-02[4] The P_MUL dissector could crash. Bug
       15337[5]. CVE-2019-5717[6].

     • wnpa-sec-2019-03[7] The RTSE dissector and other dissectors could
       crash. Bug 15373[8]. CVE-2019-5718[9].

     • wnpa-sec-2019-04[10] The ISAKMP dissector could crash. Bug
       15374[11]. CVE-2019-5719[12].

   The following bugs have been fixed:

     • console.lua not found in a folder with non-ASCII characters in
       its name. Bug 15118[13].

     • Disabling Update list of packets in real time. will generally
       trigger crash after three start capture, stop capture cycles. Bug
       15263[14].

     • UDP Multicast Stream double counts. Bug 15271[15].

     • text2pcap et al. set snaplength to 64kiB-1, while processing
       frames of 256kiB. Bug 15292[16].

     • Builds without libpcap fail if the libpcap headers aren’t
       installed. Bug 15317[17].

     • TCAP AnalogRedirectRecord parameter incorrectly coded as
       mandatory in QualReq_rr message. Bug 15350[18].

     • macOS DMG appears to have duplicate files. Bug 15361[19].

     • Wireshark jumps behind other windows when opening UAT dialogs.
       Bug 15366[20].

     • Pathnames containing non-ASCII characters are mangled in error
       dialogs on Windows. Bug 15367[21].

     • Executing -z http,stat -r file.pcapng throws a segmentation
       fault. Bug 15369[22].

     • IS-41 TCAP RegistrationNotification Invoke has borderCellAccess
       parameter coded as tag 50 (as denyAccess) but should be 58. Bug
       15372[23].

     • In DNS statistics, response times > 1 sec not included. Bug
       15382[24].

     • GTPv2 APN dissect problem. Bug 15383[25].

  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

   6LoWPAN, ANSI MAP, DNP3, DNS, GSM A, GTP, GTPv2, IMF, ISAKMP, ISObus
   VT, Kerberos, P_MUL, RTSE, S7COMM, and TCAP

  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.

  Major API Changes

     • Lua: on Windows, file-related functions such as dofile now assume
       UTF-8 paths instead of the local code page. This is consistent
       with Linux and macOS and improves compatibility on non-English
       systems. (Bug 15118[26])

 Getting Wireshark

  Wireshark source code and installation packages are available from
  https://www.wireshark.org/download.html[27].

  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[28] 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[29].

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

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

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

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

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

 Getting Help

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

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

 Frequently Asked Questions

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

  Last updated 2019-01-08 19:35:16 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2019-01
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15217
   3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5716
   4. https://www.wireshark.org/security/wnpa-sec-2019-02
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15337
   6. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5717
   7. https://www.wireshark.org/security/wnpa-sec-2019-03
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15373
   9. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5718
  10. https://www.wireshark.org/security/wnpa-sec-2019-04
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15374
  12. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5719
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15118
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15263
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15271
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15292
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15317
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15350
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15361
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15366
  21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15367
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15369
  23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15372
  24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15382
  25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15383
  26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15118
  27. https://www.wireshark.org/download.html
  28. https://www.wireshark.org/download.html#thirdparty
  29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  31. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  32. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  33. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  34. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  35. https://ask.wireshark.org/
  36. https://www.wireshark.org/lists/
  37. http://www.wiresharktraining.com/
  38. https://www.wireshark.org/faq.html


Digests

wireshark-2.6.6.tar.xz: 28407404 bytes
SHA256(wireshark-2.6.6.tar.xz)=487933ea075bdbb25d8df06017d9c4f49fc20eb7f6ec80af086718ed5550e863
RIPEMD160(wireshark-2.6.6.tar.xz)=5c5750e277e647a58916229f19d883a99e31046a
SHA1(wireshark-2.6.6.tar.xz)=d3d2f45a85e6f43a69c745b5c733e70dbc8cc535

Wireshark-win64-2.6.6.exe: 60015792 bytes
SHA256(Wireshark-win64-2.6.6.exe)=e440a059fba3572000b5695ca89438d5765b9d73d830556344d7e8cdad071617
RIPEMD160(Wireshark-win64-2.6.6.exe)=74c33427b0527fc05c4e97a94177f6895ad72beb
SHA1(Wireshark-win64-2.6.6.exe)=597a32ada9c2c51dae6b6c1e881ca50f74081136

Wireshark-win32-2.6.6.exe: 54286272 bytes
SHA256(Wireshark-win32-2.6.6.exe)=a76e70694b1914c3bf2c5267c234d44db58a605b88c274473368cb57b4262c1f
RIPEMD160(Wireshark-win32-2.6.6.exe)=a5df535decec4304088c4f9b6c219e212ab0ba9a
SHA1(Wireshark-win32-2.6.6.exe)=0826853320be66fc8afbc5f9d2520de5a96e92d3

Wireshark-win64-2.6.6.msi: 49385472 bytes
SHA256(Wireshark-win64-2.6.6.msi)=9ca2a067f33f551da479a2b760a943f340e6996db155832ba1c486e3c3afe272
RIPEMD160(Wireshark-win64-2.6.6.msi)=e93c8fa321d521517b12bb0704e4c27df566243e
SHA1(Wireshark-win64-2.6.6.msi)=d9b5558c052c6db9caa5bd294ff61965e0a79dce

Wireshark-win32-2.6.6.msi: 43753472 bytes
SHA256(Wireshark-win32-2.6.6.msi)=a700512870239f5b17311eab223eaf319e17c8d66d1676aa5327c2c5688b17c6
RIPEMD160(Wireshark-win32-2.6.6.msi)=285f2f2d8417e3730df84fcef556b77c993159e4
SHA1(Wireshark-win32-2.6.6.msi)=e7008b63cd6c7223a8456234dc49517ca7f40810

WiresharkPortable_2.6.6.paf.exe: 37492944 bytes
SHA256(WiresharkPortable_2.6.6.paf.exe)=8003dd25e6971cc97350df4c715ad56be873930f08328dbeee253349808cc0ae
RIPEMD160(WiresharkPortable_2.6.6.paf.exe)=58013de0b67d5c5cad6ae6d779aacfb53ce4b532
SHA1(WiresharkPortable_2.6.6.paf.exe)=624aa86801388b715db2cebfcd21376a6d75cbca

Wireshark 2.6.6 Intel 64.dmg: 108149698 bytes
SHA256(Wireshark 2.6.6 Intel
64.dmg)=71920bf98e2867703759b0c98395480f88dee1c332efd3f2bc6a91eaec75b0a3
RIPEMD160(Wireshark 2.6.6 Intel
64.dmg)=42a33054c01bbdd1834c93970b26967954053d42
SHA1(Wireshark 2.6.6 Intel 64.dmg)=45d4d188b151caf11724435640344c02f9746f9b

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