Wireshark · Wireshark-announce: [Wireshark-announce] Wireshark 2.6.14 is now available

[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 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 bugs have been fixed:

     • Buildbot crash output: randpkt-2019-11-30-22633.pcap. Bug
       16240[1].

     • Crash after closing the Edit Column widget. Bug 16245[2].

     • Some valid erf timestamps get confused for gzip magic header
       bytes and causes an error with file_seek. Bug 16252[3].

     • [UDS] When filtering the uds.rdbi.data_identifier field is
       interpreted as 1 byte whereas it consists of 2 bytes. Bug
       16256[4].

     • DNS time to live field should be displayed as
       days/hours/minutes/seconds. Bug 16263[5].

     • LNet incorrectly displays Malformed Packet for RDMA Read
       Requests. Bug 16269[6].

     • 11ad packets get reported as 11n. Bug 16272[7].

     • MPLS : Label Stack Sub TLV decoded improperly. Bug 16273[8].

     • h264: SPS frame_crop_right_offset shown in UI as
       frame_crop_left_offset. Bug 16285[9].

  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

   802.11 Radiotap, DNS, GSM A RR, H264, LNET, MPLS Echo, TIPC, and UDSG

  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.

 Getting Wireshark

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

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

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

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

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

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

 Getting Help

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

 Frequently Asked Questions

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

  Last updated 2020-01-13 23:28:13 UTC

 References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16240
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16245
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16252
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16256
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16263
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16269
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16272
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16273
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16285
  10. https://www.wireshark.org/download.html#thirdparty
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
  13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  15. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  16. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  17. https://ask.wireshark.org/
  18. https://www.wireshark.org/lists/
  19. https://www.wireshark.org/faq.html


Digests

wireshark-2.6.14.tar.xz: 28500904 bytes
SHA256(wireshark-2.6.14.tar.xz)=c4d133c48f52d81fc334c30fa21e09be484d862c29310e57fc2532e5b572e9c4
RIPEMD160(wireshark-2.6.14.tar.xz)=d1179c901bb02ed68cc4c90cb0318ec0ba928365
SHA1(wireshark-2.6.14.tar.xz)=8f5a1afb7c041c81777680a29332f64cdbdc50c4

Wireshark-win32-2.6.14.exe: 54058640 bytes
SHA256(Wireshark-win32-2.6.14.exe)=18dfe83487f30a039154a90fa9cb2496342d2beff21212139ea46ab9561fa2c1
RIPEMD160(Wireshark-win32-2.6.14.exe)=8b043bd7a7f165c5a6ab69e32f022ba08aaa0f38
SHA1(Wireshark-win32-2.6.14.exe)=54d92f7f05a9b73d2095f0c155eabd051a82e87a

Wireshark-win64-2.6.14.exe: 59698592 bytes
SHA256(Wireshark-win64-2.6.14.exe)=4a5fd7ee319b4371520277a520ae5be79e62508a128c46d1b779f1ff144c37d3
RIPEMD160(Wireshark-win64-2.6.14.exe)=f44e5f4fd9f2facf16c84470f4fd3877f12fc57a
SHA1(Wireshark-win64-2.6.14.exe)=34005572bf373bb7dd3d81b2bce9694fe8b3f297

Wireshark-win32-2.6.14.msi: 43565056 bytes
SHA256(Wireshark-win32-2.6.14.msi)=f2c36311360039a673123e1b167c88b50de7d357885c33b57bd8597fabd4a978
RIPEMD160(Wireshark-win32-2.6.14.msi)=3f122d013e36399b3df175f6b49033051eca7b96
SHA1(Wireshark-win32-2.6.14.msi)=65e259c2b046f4584700c3fdcffd07c4ceeb4a66

Wireshark-win64-2.6.14.msi: 49311744 bytes
SHA256(Wireshark-win64-2.6.14.msi)=aa21346f91469a6a667c519621f2bf8eebbf3cc39cecd885d78fd6c09dc9ea94
RIPEMD160(Wireshark-win64-2.6.14.msi)=52e9b89335c7b4b5fabfa4c390572c82a1ef2134
SHA1(Wireshark-win64-2.6.14.msi)=daeef09ec9ef9de12fa5c41d13b6eb8c8432724f

WiresharkPortable_2.6.14.paf.exe: 37290928 bytes
SHA256(WiresharkPortable_2.6.14.paf.exe)=1c2059f4e77ae33b81627b8a778ed6c92cd8e746e6b8675c29d05f22802f80fa
RIPEMD160(WiresharkPortable_2.6.14.paf.exe)=1bbccf08bfa75a0184448d5912b0a03a7e8e749b
SHA1(WiresharkPortable_2.6.14.paf.exe)=3ed05da96ebacdc0344a6fb5b7fbe6f8ec765f3a

Wireshark 2.6.14 Intel 64.dmg: 108215399 bytes
SHA256(Wireshark 2.6.14 Intel 64.dmg)=ea04f8ca05c2e84426221650edc629868a3395cc9ad5cdf56f1c743f564263bd
RIPEMD160(Wireshark 2.6.14 Intel 64.dmg)=332567d92b41b4cbbbd6904bcd04a6b5b4199c92
SHA1(Wireshark 2.6.14 Intel 64.dmg)=5982b1fdac1265e83a1e504be3beef6578baf06c

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