Wireshark · Wireshark-users: [Wireshark-users] Wireshark 2.2.17 is now available

[Gerald Combs <gerald@xxxxxxxxxxxxx>]

I'm proud to announce the release of Wireshark 2.2.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

   This is the final release of Wireshark 2.2. It will reach its official
   end of life on September 7, 2018. If you are still using Wireshark 2.2
   you are encouraged to upgrade to Wireshark 2.6.

  Bug Fixes

   The following vulnerabilities have been fixed:
     * [1]wnpa-sec-2018-44
       Bluetooth AVDTP dissector crash. [2]Bug 14884. [3]CVE-2018-16058.
     * [4]wnpa-sec-2018-45
       Bluetooth Attribute Protocol dissector crash. [5]Bug 14994.
       [6]CVE-2018-16056.
     * [7]wnpa-sec-2018-46
       Radiotap dissector crash. [8]Bug 15022. [9]CVE-2018-16057.

   The following bugs have been fixed:
     * udpdump frame too long error. [10]Bug 14989.
     * ASTERIX Category 062 / 135 Altitude has wrong value. [11]Bug 15030.
     * Wireshark cannot decrypt SSL/TLS session if it was proxied over
       HTTP tunnel. [12]Bug 15042.
     * TLS records in a HTTP tunnel are displayed as "Encrypted Handshake
       Message". [13]Bug 15043.
     * Diameter AVP User Location Info, Mobile Network Code decoded not
       correctly. [14]Bug 15068.
     * Heartbeat message "Info" displayed without comma separator. [15]Bug
       15079.

  New and Updated Features

   There are no new features in this release.

  New File Format Decoding Support

   There are no new file formats in this release.

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   ASTERIX, Bluetooth ATT, Bluetooth AVDTP, DTLS, E.212, HTTP, K12, and
   Radiotap

  New and Updated Capture File Support

   pcapng

  New and Updated Capture Interfaces support

   ciscodump

  Major API Changes

   There are no major API changes in this release.
     __________________________________________________________________

Getting Wireshark

   Wireshark source code and installation packages are available from
   [16]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 [17]download page 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

   Dumpcap might not quit if Wireshark or TShark crashes. ([18]Bug 1419)

   The BER dissector might infinitely loop. ([19]Bug 1516)

   Capture filters aren't applied when capturing from named pipes.
   ([20]Bug 1814)

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

   Application crash when changing real-time option. ([22]Bug 4035)

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

   Wireshark should let you work with multiple capture files. ([24]Bug
   10488)
     __________________________________________________________________

Getting Help

   Community support is available on [25]Wireshark's Q&A site and on the
   wireshark-users mailing list. Subscription information and archives for
   all of Wireshark's mailing lists can be found on [26]the web site.

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

Frequently Asked Questions

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

   Last updated 2018-08-29 16:53:25 UTC

References

   1. https://www.wireshark.org/security/wnpa-sec-2018-44.html
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14884
   3. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16058
   4. https://www.wireshark.org/security/wnpa-sec-2018-45.html
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14994
   6. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16056
   7. https://www.wireshark.org/security/wnpa-sec-2018-46.html
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15022
   9. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16057
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14989
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15030
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15042
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15043
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15068
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15079
  16. https://www.wireshark.org/download.html
  17. https://www.wireshark.org/download.html#thirdparty
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  23. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  24. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  25. https://ask.wireshark.org/
  26. https://www.wireshark.org/lists/
  27. http://www.wiresharktraining.com/
  28. https://www.wireshark.org/faq.html


Digests

wireshark-2.2.17.tar.bz2: 32551027 bytes
SHA256(wireshark-2.2.17.tar.bz2)=923d39ff9c6df83b9594868542061da33bf330e12526778a8cb3adcf912eebb0
RIPEMD160(wireshark-2.2.17.tar.bz2)=06086c787720d126be5d47411b601ff59d9f4ba9
SHA1(wireshark-2.2.17.tar.bz2)=ed21da5b2348d47560481937243821ce1faab724

Wireshark-win64-2.2.17.exe: 56211152 bytes
SHA256(Wireshark-win64-2.2.17.exe)=49df6f1b64a9d68b4c6c2491781b74f2f09f71fd616d2ddbd8f413bab2aad413
RIPEMD160(Wireshark-win64-2.2.17.exe)=e80720bd8c0c0dbaf1a02215b3f2f29a3c110585
SHA1(Wireshark-win64-2.2.17.exe)=2f0864c932aaecb887ed14a67ec8a033b2ad411c

Wireshark-win32-2.2.17.exe: 44707592 bytes
SHA256(Wireshark-win32-2.2.17.exe)=e50bf2aa9560c3a1052a9179f26f729acf27e929836d98937605d14b69fe2f2f
RIPEMD160(Wireshark-win32-2.2.17.exe)=c796a9bf7dd0f1a481fc0d7698bf842c9ddb4a29
SHA1(Wireshark-win32-2.2.17.exe)=c86f0622740d07e25ccd5e02c215392ec3f6d4ce

WiresharkPortable_2.2.17.paf.exe: 46336584 bytes
SHA256(WiresharkPortable_2.2.17.paf.exe)=1e627c1422e127ab5d558b60e321297d3391b35cbb370afa4fcc8a5fea128819
RIPEMD160(WiresharkPortable_2.2.17.paf.exe)=7c2f118739fdc5feeef3f75b1876f948c1c39de0
SHA1(WiresharkPortable_2.2.17.paf.exe)=a7d445f6f980cd69504f2b8d452258031a906f1c

Wireshark 2.2.17 Intel 64.dmg: 40014949 bytes
SHA256(Wireshark 2.2.17 Intel
64.dmg)=fb58dd8ab1eae1d5665c340decb8e30f00d1dd1ec899330239a58d8b141ba1e5
RIPEMD160(Wireshark 2.2.17 Intel
64.dmg)=8e006530f1594216d7fc20d637a8c8ab50a12e24
SHA1(Wireshark 2.2.17 Intel 64.dmg)=9bec5f176a2347bd9c76760405d24a3a7e5f27a6

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