[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 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:

   The following bugs have been fixed:

     • Windows Uninstall does not remove all files in Program Files. Bug
       16601[1].

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

     • Decode as not working correctly with multiple user profiles. Bug
       16635[3].

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

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

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

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

  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, CoAP, 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[8] 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.

 Getting Help

  The User’s Guide, manual pages and various other documentation can be
  found at https://www.wireshark.org/docs/

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

  Bugs and feature requests can be reported on the bug tracker[11].

 Frequently Asked Questions

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

  Last updated 2020-07-01 18:22:50 UTC

 References

   1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16601
   2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16604
   3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16635
   4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16636
   5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16639
   6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16642
   7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16652
   8. https://www.wireshark.org/download.html#thirdparty
   9. https://ask.wireshark.org/
  10. https://www.wireshark.org/lists/
  11. https://bugs.wireshark.org/
  12. https://www.wireshark.org/faq.html


Digests

wireshark-3.0.12.tar.xz: 30922372 bytes
SHA256(wireshark-3.0.12.tar.xz)=fafcea16eef1aaf9f7bd7aeb2db68b47a4ab43a7808f1d42a06a7b02c47bc764
RIPEMD160(wireshark-3.0.12.tar.xz)=85a88cb7874148867186e0ff75b3eebd28875916
SHA1(wireshark-3.0.12.tar.xz)=ed017cd9d3c9e535a04ab53751e36b0a3d8d5a53

Wireshark-win32-3.0.12.exe: 54081312 bytes
SHA256(Wireshark-win32-3.0.12.exe)=541bf2b3da6aa580f6ac9bc2f59ea2db7bc57b688afb25f24fe708739ad271e9
RIPEMD160(Wireshark-win32-3.0.12.exe)=721006410838708b9f4969cc5e0fd837c9ed1a33
SHA1(Wireshark-win32-3.0.12.exe)=dcd2cae4accab934b1050ea99c9350449f3eb1e3

Wireshark-win64-3.0.12.exe: 59286976 bytes
SHA256(Wireshark-win64-3.0.12.exe)=7ea8204d9482b3c9b8d57c88197f73704271db26b5e9c39705c20455271c28aa
RIPEMD160(Wireshark-win64-3.0.12.exe)=b1f86f88da31a97aa81292e669be8cc1c510676a
SHA1(Wireshark-win64-3.0.12.exe)=30d63612aab6cd640f754d5153739b54f4a40428

Wireshark-win64-3.0.12.msi: 47271936 bytes
SHA256(Wireshark-win64-3.0.12.msi)=34f0ed6e086677f0ef7b98e9f44060c789efb43329cfd402122334a0f9735197
RIPEMD160(Wireshark-win64-3.0.12.msi)=4796a7e535e0adf2a75a398e45a26a8cf28c9c5a
SHA1(Wireshark-win64-3.0.12.msi)=6045358a1b38c28f8c78bb75143d141b77b61919

Wireshark-win32-3.0.12.msi: 42065920 bytes
SHA256(Wireshark-win32-3.0.12.msi)=d32d22d5a513bab480af746f3f56dd9d3030b34771df4f785d87fb6a9b4bee3a
RIPEMD160(Wireshark-win32-3.0.12.msi)=dbc371fc28483f5fde14dfaa0d0179996f19b83d
SHA1(Wireshark-win32-3.0.12.msi)=837ca34d78fec1e315337fc5f148940b7f4898ad

WiresharkPortable_3.0.12.paf.exe: 35845152 bytes
SHA256(WiresharkPortable_3.0.12.paf.exe)=62619ab9c8e8c0d64198234fa1d4e48cfb60c3b05207eeb5972ccf0b1a4eb6ce
RIPEMD160(WiresharkPortable_3.0.12.paf.exe)=33f5469fe124c24c50d19b662d291f3f250fd842
SHA1(WiresharkPortable_3.0.12.paf.exe)=08455fc14a3522bf9abc20a4ab65b3e29aa9e3ae

Wireshark 3.0.12 Intel 64.dmg: 93141894 bytes
SHA256(Wireshark 3.0.12 Intel 64.dmg)=144ef75b0b78dad2eef7da5ba13ece51828d4662716ed048ceddaf714488383b
RIPEMD160(Wireshark 3.0.12 Intel 64.dmg)=2142346b7335fddf011ae14dbdf424a8e55985bc
SHA1(Wireshark 3.0.12 Intel 64.dmg)=0166e50803817cfad2b9f93616096de5bb3615ee

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