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

 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:

     • The "relative sequence number" is same as "raw sequence number"
       when tcp.analyze_sequence_numbers:FALSE. Bug 16604[1].

     • Wireshark can misdissect the HE Radiotap field if it’s ever
       dissected one with any value unknown. Bug 16636[2].

     • Buildbot crash output: fuzz-2020-06-19-5981.pcap. Bug 16639[3].

     • Buildbot crash output: fuzz-2020-06-20-7665.pcap. Bug 16642[4].

     • mergecap man page contains invalid formatting. Bug 16652[5].

  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

   ASTERIX, GSM RR, GTPv2, R3, Radiotap, RTPS, and TCP

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

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

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

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

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

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

 Getting Help

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

 Frequently Asked Questions

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

  Last updated 2020-07-01 18:24:08 UTC

 References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16604
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16636
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16639
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16642
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16652
   6. https://www.wireshark.org/download.html#thirdparty
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1516
   8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1814
   9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234
  10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4035
  11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4985
  12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10488
  13. https://ask.wireshark.org/
  14. https://www.wireshark.org/lists/
  15. https://www.wireshark.org/faq.html


Digests

wireshark-2.6.18.tar.xz: 28553028 bytes
SHA256(wireshark-2.6.18.tar.xz)=52b4f119e12b9d0aa8a79ffc9d98215f0711f1ce9935f1d15c643d2486ba7740
RIPEMD160(wireshark-2.6.18.tar.xz)=d081a901d7bf03f174287fe011d35e99a25815f4
SHA1(wireshark-2.6.18.tar.xz)=85da670d36a3c4369dbdbb5e2fe52c47b70e3abd

Wireshark-win32-2.6.18.exe: 54102456 bytes
SHA256(Wireshark-win32-2.6.18.exe)=b68d38bc466f657c8f92e2d676ea70394c9505025a8db98f17e70f5e535b90ad
RIPEMD160(Wireshark-win32-2.6.18.exe)=606471720362512c70b78b585d74a267f4e6f349
SHA1(Wireshark-win32-2.6.18.exe)=97185126b1b8cccb520bae8c4c371a7607651d03

Wireshark-win64-2.6.18.exe: 59741880 bytes
SHA256(Wireshark-win64-2.6.18.exe)=9be3ad4d7a6a2ce92c027d22fd4f6e1ebd5edd9b0422fa01da7c6cc87d566ae5
RIPEMD160(Wireshark-win64-2.6.18.exe)=616aca3c111b76cd440311097f1c941d7db25acc
SHA1(Wireshark-win64-2.6.18.exe)=7f0c95fceb7ddc87c6123f22f5edf17b5de28d9a

Wireshark-win64-2.6.18.msi: 49209344 bytes
SHA256(Wireshark-win64-2.6.18.msi)=f54e97d7d5707ec58980fee9b988749f34d9fe4b7289f830bf4c8971efdfac28
RIPEMD160(Wireshark-win64-2.6.18.msi)=e1d0e2482b07767df3d9ba28eb85d581c35571cb
SHA1(Wireshark-win64-2.6.18.msi)=81c9263f66af4de8b1758c4cae19452a1f2af6a5

Wireshark-win32-2.6.18.msi: 43610112 bytes
SHA256(Wireshark-win32-2.6.18.msi)=e8ffdff52dfbf6b8ccb695b3dfb748a2c90a63bead747019f7f2078ad14852c9
RIPEMD160(Wireshark-win32-2.6.18.msi)=a2f00c30c7ecb0ca2818e25edb607d68a3e07e42
SHA1(Wireshark-win32-2.6.18.msi)=79f3f71765232631f5ddcc85b1d7eec351da3203

WiresharkPortable_2.6.18.paf.exe: 37345624 bytes
SHA256(WiresharkPortable_2.6.18.paf.exe)=557af198c7540231853516a0967a15d1c900b91d32530143c013bb1588cf5a93
RIPEMD160(WiresharkPortable_2.6.18.paf.exe)=9c34948d3fb0c2c8eb48b1716ca1e400fcc17db4
SHA1(WiresharkPortable_2.6.18.paf.exe)=53a2440ee744733c4e97b7bebadd936fdf1421c3

Wireshark 2.6.18 Intel 64.dmg: 108270907 bytes
SHA256(Wireshark 2.6.18 Intel 
64.dmg)=3be00722654d7064a4e55b4c35ee77e02af8cc387efb433240608380b25b7719
RIPEMD160(Wireshark 2.6.18 Intel 
64.dmg)=2bbae7f55644c639c52b0141acfe716d55f4d133
SHA1(Wireshark 2.6.18 Intel 64.dmg)=7b0be54c6bf3581fcdc88fe3dac64ba027f00178

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

___________________________________________________________________________
Sent via:    Wireshark-announce mailing list <wireshark-announce@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-announce
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-announce
             mailto:wireshark-announce-requ...@wireshark.org?subject=unsubscribe

Reply via email to