[Gerald Combs <gerald@xxxxxxxxxxxxx>]

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

     __________________________________________________________________

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:
     * [1]wnpa-sec-2018-25
       The LDSS dissector could crash. ([2]Bug 14615)
     * [3]wnpa-sec-2018-28
       Multiple dissectors could consume excessive memory. ([4]Bug 14678)
     * [5]wnpa-sec-2018-29
       The DNS dissector could crash. ([6]Bug 14681)
     * [7]wnpa-sec-2018-30
       The GSM A DTAP dissector could crash. ([8]Bug 14688)
     * [9]wnpa-sec-2018-31
       The Q.931 dissector could crash. ([10]Bug 14689)
     * [11]wnpa-sec-2018-33
       Multiple dissectors could crash. ([12]Bug 14703)

   The following bugs have been fixed:
     * SMB2 Write requests not displayed. ([13]Bug 14598)
     * Wrong default file format chosen in when saving a capture with
       comments added if the original format doesn't support comments.
       ([14]Bug 14601)
     * WinSparkle 0.5.6 is out of date and is buggy. ([15]Bug 14642)

  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

   BATADV, BSSMAP, BVLC, DNS, GSM A DTAP, GTP, IEEE 802.11, LDSS, Logcat
   Text, MP2T, MPEG PES, NBSS, Q.931, and S7COMM

  New and Updated Capture File Support

   3GPP TS 32.423 Trace, and Android Logcat

  New and Updated Capture Interfaces support

   There are no new or updated capture interfaces supported in this
   release.

  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-05-21 20:14:12 UTC

References

   1. https://www.wireshark.org/security/wnpa-sec-2018-25.html
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14615
   3. https://www.wireshark.org/security/wnpa-sec-2018-28.html
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14678
   5. https://www.wireshark.org/security/wnpa-sec-2018-29.html
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14681
   7. https://www.wireshark.org/security/wnpa-sec-2018-30.html
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14688
   9. https://www.wireshark.org/security/wnpa-sec-2018-31.html
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14689
  11. https://www.wireshark.org/security/wnpa-sec-2018-33.html
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14703
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14598
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14601
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14642
  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.15.tar.bz2: 32468902 bytes
SHA256(wireshark-2.2.15.tar.bz2)=d73583e9282d47c42b69fc3a1ac9cafb6047d1305f5027d4cf18e95922d11844
RIPEMD160(wireshark-2.2.15.tar.bz2)=b2ec0d7dc270e164b699dfabae2b32880047be31
SHA1(wireshark-2.2.15.tar.bz2)=4a24d475d57431d315436763111133d330d1e911

Wireshark-win32-2.2.15.exe: 44677248 bytes
SHA256(Wireshark-win32-2.2.15.exe)=263911cdf9bd40246349e768ea0e169a4805213e9e874901f682691fbc590877
RIPEMD160(Wireshark-win32-2.2.15.exe)=c0c44c46fcc3236e4d237044f82c7b9c5ead547b
SHA1(Wireshark-win32-2.2.15.exe)=dae3c680526794ecbde92913867cda261663d181

Wireshark-win64-2.2.15.exe: 56181536 bytes
SHA256(Wireshark-win64-2.2.15.exe)=61bbef29ee89045dbf897f2d2909d0992b86e62068a4972d06f34124ead8e06a
RIPEMD160(Wireshark-win64-2.2.15.exe)=de2180034d3ea9547011a318281c78cca61657c2
SHA1(Wireshark-win64-2.2.15.exe)=65c5a80738564aea1542349bcbe05b45e4135436

WiresharkPortable_2.2.15.paf.exe: 46309704 bytes
SHA256(WiresharkPortable_2.2.15.paf.exe)=444e8e508a7677cc56a2f9afe2e76680b346776bdfe03cf830dd74de783e11df
RIPEMD160(WiresharkPortable_2.2.15.paf.exe)=da998bbbea9e3ffe32958ce0957520ce2cbf89bf
SHA1(WiresharkPortable_2.2.15.paf.exe)=e175c39eec7ad7c91e1b84ef21c2c0d76ed88249

Wireshark 2.2.15 Intel 64.dmg: 39984252 bytes
SHA256(Wireshark 2.2.15 Intel
64.dmg)=780afdb27e4cb9133dd52603e1e4a2d6005bfb356bad88090e9e0ccd54ece376
RIPEMD160(Wireshark 2.2.15 Intel
64.dmg)=dce335a226202fc1c869bf0cdf89b498fe73565c
SHA1(Wireshark 2.2.15 Intel 64.dmg)=19dd914d517c117f9d3a1718c45e8db89e95213a

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