[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 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.5. Previously they
      shipped with Qt 5.9.4.

  Bug Fixes

   The following vulnerabilities have been fixed:

     • ws-sa2018-25

     • The LDSS dissector could crash. (ws-bug14615)

     • ws-sa2018-26

     • The IEEE 1905.1a dissector could crash. (ws-bug14647)

     • ws-sa2018-27

     • The RTCP dissector could crash. (ws-bug14673)

     • ws-sa2018-28

     • Multiple dissectors could consume excessive memory. (ws-bug14678)

     • ws-sa2018-29

     • The DNS dissector could crash. (ws-bug14681)

     • ws-sa2018-30

     • The GSM A DTAP dissector could crash. (ws-bug14688)

     • ws-sa2018-31

     • The Q.931 dissector could crash. (ws-bug14689)

     • ws-sa2018-32

     • The IEEE 802.11 dissector could crash. (ws-bug14686)

     • ws-sa2018-33

     • Multiple dissectors could crash. (ws-bug14703)

   The following bugs have been fixed:

     • Qt GUI does not snap to exactly half of screen in Windows. (Bug
       13516[1])

     • Segmentation fault when switching profiles. (Bug 14316[2])

     • QUIC dissector produces incorrect packet numbers (wrong-endian).
       (Bug 14462[3])

     • Wrong default file format chosen in when saving a capture with
       comments added if the original format doesn’t support comments.
       (Bug 14601[4])

     • Lua: Error during loading [AppData directory]:1: bad argument #1
       to dofile (dofile: file does not exist). (Bug 14619[5])

     • Crash when selecting text. (Bug 14620[6])

     • ui/macosx directory missing from source release tarball. (Bug
       14627[7])

     • Wireshark 2.9.0 snapshot crashes/segfaults on Windows when
       launched with -k or -i. (Bug 14632[8])

     • "Copy as printable text" isn’t copying non-alphanumeric
       characters. (Bug 14633[9])

     • File missing from release tarball. (Bug 14634[10])

     • NEWS is out of date and does not display properly in Notepad.
       (Bug 14636[11])

     • l16mono.so is installed in the wrong place. (Bug 14638[12])

     • Remove: HACK to support UHD’s weird header offset on data
       packets. (Bug 14641[13])

     • WinSparkle 0.5.6 is out of date and is buggy. (Bug 14642[14])

     • Unable to create or open VOIP captures. (Bug 14648[15])

     • RTMPT: incorrect dissection of multiple RTMP packets within a
       single TCP packet. (Bug 14650[16])

     • Endpoints dialog displays invalid GeoIP information due to
       incorrect byte order. (Bug 14656[17])

     • Qt: Crash in ShowPacketBytesDialog(). (Bug 14658[18])

     • Statistics → Resolved addresses show IP addresses without domain.
       (Bug 14667[19])

     • Erroneous MAC-LTE Dissection for Sidelink Shared Channel Packets.
       (Bug 14669[20])

     • Files missing from docbook CMake file. (Bug 14676[21])

     • Wireshark hangs when opening certain files if it’s been
       configured to use the new GeoIP databases. (Bug 14701[22])

   The “Open”, “Save”, and other file dialogs should now be shown at the
   correct size on HiDPI Windows systems.

  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

   BATADV, BT LE LL, CoAP, DNS, DTLS, GSM A DTAP, GSM A GM, GTP, GTPv2,
   IEEE 1905.1a, IEEE 802.11, LDSS, LwM2M-TLV, MAC LTE, NAS EPS, Q.931,
   RTCP, RTMPT, SDP, TCP, and VITA 49

  New and Updated Capture File Support

   3GPP TS 32.423 Trace and Android Logcat

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

  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[24] 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[25])

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

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

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

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

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

 Getting Help

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

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

 Frequently Asked Questions

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

  Last updated 2018-05-22 17:55:18 UTC

 References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13516
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14316
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14462
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14601
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14619
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14620
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14627
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14632
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14633
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14634
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14636
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14638
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14641
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14642
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14648
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14650
  17. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14656
  18. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14658
  19. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14667
  20. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14669
  21. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14676
  22. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14701
  23. https://www.wireshark.org/download.html
  24. https://www.wireshark.org/download.html#thirdparty
  25. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  26. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  27. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  28. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  29. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  30. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  31. https://ask.wireshark.org/
  32. https://www.wireshark.org/lists/
  33. http://www.wiresharktraining.com/
  34. https://www.wireshark.org/faq.html


Digests

wireshark-2.6.1.tar.xz: 28386244 bytes
SHA256(wireshark-2.6.1.tar.xz)=ab6e5bbc3464c956347b8671ce8397950ad5daff3bf9964c967d495f4ddbcd88
RIPEMD160(wireshark-2.6.1.tar.xz)=a7f187de0c44b801b51e8b72df41681bbc1835f8
SHA1(wireshark-2.6.1.tar.xz)=a0cf45d99ab9a42e087af150cbdec08650b9977a

Wireshark-win64-2.6.1.exe: 59945592 bytes
SHA256(Wireshark-win64-2.6.1.exe)=7fea0e6edf6e6a10d277a354fc9982c6d15c2f2aa05ec13c714e077b8c8760a9
RIPEMD160(Wireshark-win64-2.6.1.exe)=8dd17fbbd6a149aa17a264bd32c5cc39e6d5211c
SHA1(Wireshark-win64-2.6.1.exe)=af58ff12b234d4c811eb2828a174a10780d23817

Wireshark-win32-2.6.1.exe: 54228352 bytes
SHA256(Wireshark-win32-2.6.1.exe)=f1e2a07e696338217671b58076073ad3a8ae165ece7fcb71866b6dcc750e1bf8
RIPEMD160(Wireshark-win32-2.6.1.exe)=9c389d37d93cc70d04c73b0a537766b0c163108b
SHA1(Wireshark-win32-2.6.1.exe)=ca6030711d0d1cec2c93c7daace448f7f70ed6f4

Wireshark-win32-2.6.1.msi: 43700224 bytes
SHA256(Wireshark-win32-2.6.1.msi)=fe77af67c5816899b42decde78e6561aa6f03c5ad8adf7dc58225864afae2a09
RIPEMD160(Wireshark-win32-2.6.1.msi)=9e460ca8927220f31280376663a9093ecb3cd5e6
SHA1(Wireshark-win32-2.6.1.msi)=ac0271ec30a8548ac1207689f81443bb6262037f

Wireshark-win64-2.6.1.msi: 49356800 bytes
SHA256(Wireshark-win64-2.6.1.msi)=1796964f494a869719bb47075f9bc16d505d6f67b6f423df865ab5191b6b0c02
RIPEMD160(Wireshark-win64-2.6.1.msi)=2d45528c02e56078b00f3a36c61ce3e02832b98d
SHA1(Wireshark-win64-2.6.1.msi)=27d5e6075d1b9c5ae680df622bcd77da0cb33048

WiresharkPortable_2.6.1.paf.exe: 37458264 bytes
SHA256(WiresharkPortable_2.6.1.paf.exe)=b2bc490dd42aae080543728d9787bff650996e965f6cac0d700fa3ac79bf9981
RIPEMD160(WiresharkPortable_2.6.1.paf.exe)=ebec0ef8612cead98f37898f0a16e8f2de451b4a
SHA1(WiresharkPortable_2.6.1.paf.exe)=7350f3f51eae5a2be9b6d4566ad8e42d16cb0968

Wireshark 2.6.1 Intel 64.dmg: 168940751 bytes
SHA256(Wireshark 2.6.1 Intel
64.dmg)=bf5f9a0e810a7cfb360ea69b1b587126432adffe5fa65db902fa761842b55a6a
RIPEMD160(Wireshark 2.6.1 Intel
64.dmg)=540f43bf5d541e7441db61a565d0504a5615ef3c
SHA1(Wireshark 2.6.1 Intel 64.dmg)=56025bb522b9cd35c82c05901227301a4de40acb

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