[Wireshark announcements <wireshark-announce@xxxxxxxxxxxxx>]

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


 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

     • wnpa-sec-2020-14[1] FBZERO dissector crash. Bug 16887[2].

     • Infinite memory allocation while parsing this tcp packet. Bug
       16887[3].

     • wnpa-sec-2020-15[4] GQUIC dissector crash.

   The following bugs have been fixed:

     • FETCH Proactive Command SEND SHORT MESSAGE [Dissector bug,
       protocol ETSI CAT: Bug 16889[5].

     • wireshark-3.3.1/epan/dissectors/packet-e212.c:3297: possible
       wrong operator ? Bug 16895[6].

     • Bison 3.0 causes build failures Bug 16924[7].

     • MATE not extracting fields as requested Bug 16961[8].

  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

   E.212, ETSI CAT, FBZERO, GQUIC, GSM A RR, ICMP, IEEE 802.11, LCSAP,
   SDAP, Thread Address, TLS, and XnAP

  New and Updated Capture File 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[9] 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[10] 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[11].

  Issues and feature requests can be reported on the issue tracker[12].

 Frequently Asked Questions

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

  Last updated 2020-10-29 19:21:56 UTC

 References

   1. https://www.wireshark.org/security/wnpa-sec-2020-14
   2. https://gitlab.com/wireshark/wireshark/-/issues/16887
   3. https://gitlab.com/wireshark/wireshark/-/issues/16887
   4. https://www.wireshark.org/security/wnpa-sec-2020-15
   5. https://gitlab.com/wireshark/wireshark/-/issues/16889
   6. https://gitlab.com/wireshark/wireshark/-/issues/16895
   7. https://gitlab.com/wireshark/wireshark/-/issues/16924
   8. https://gitlab.com/wireshark/wireshark/-/issues/16961
   9. https://www.wireshark.org/download.html#thirdparty
  10. https://ask.wireshark.org/
  11. https://www.wireshark.org/lists/
  12. https://gitlab.com/wireshark/wireshark/-/issues
  13. https://www.wireshark.org/faq.html


Digests

wireshark-3.2.8.tar.xz: 31660652 bytes
SHA256(wireshark-3.2.8.tar.xz)=a8a595d08f38c6bd083886f6c199b9d4fb007e363031b263667c7da72323cc32
RIPEMD160(wireshark-3.2.8.tar.xz)=150975c46582778575c704cd1f668f0fc341aed2
SHA1(wireshark-3.2.8.tar.xz)=5fdcbbe3a50cea38a8fa5f10b21f58cbef31793e

Wireshark-win32-3.2.8.exe: 54824688 bytes
SHA256(Wireshark-win32-3.2.8.exe)=61ff02ae14156f84df8cf6d552bb645ff5d2e39d67122422e6ef881673abe609
RIPEMD160(Wireshark-win32-3.2.8.exe)=22ebb1a2eabc0469205241a07db5b3923a2a9c58
SHA1(Wireshark-win32-3.2.8.exe)=00877975c631ddf726b94f6f233e629d2b9a4d00

Wireshark-win64-3.2.8.exe: 59974624 bytes
SHA256(Wireshark-win64-3.2.8.exe)=47e6488975dee3351a956f7201b73ff87cd290d4f04c65bdcf3baeaeba59aa2d
RIPEMD160(Wireshark-win64-3.2.8.exe)=b2808fd28b0368812467fa401e845f181e957d62
SHA1(Wireshark-win64-3.2.8.exe)=0c44bd5dcfb8fbbfe9f25558b9d199ee5b13a0c4

Wireshark-win64-3.2.8.msi: 48353280 bytes
SHA256(Wireshark-win64-3.2.8.msi)=dc50e707ffc599a747ddc1976e28780ec58286220c2c7be81d8042682e370e43
RIPEMD160(Wireshark-win64-3.2.8.msi)=bb4d5f0400775e988d15db338332d06599f6459e
SHA1(Wireshark-win64-3.2.8.msi)=99edaaafd861965148f2364264c9d31135c24e83

Wireshark-win32-3.2.8.msi: 43098112 bytes
SHA256(Wireshark-win32-3.2.8.msi)=3e0b9c2520146850aff8608cfcf3427e3fd78228166c30ca9eed17cf50787ce9
RIPEMD160(Wireshark-win32-3.2.8.msi)=b6b402422b1670ce2e7ffdf3815da9f50466bf2d
SHA1(Wireshark-win32-3.2.8.msi)=6d7ae537cd59b090d2147f9bccd566bae4045f0f

WiresharkPortable_3.2.8.paf.exe: 36697496 bytes
SHA256(WiresharkPortable_3.2.8.paf.exe)=21faab30e125340ed8545d21980a614ca7c5f92a7bcbeaa6706107277d12771e
RIPEMD160(WiresharkPortable_3.2.8.paf.exe)=7bbc0b765789192908345170b8ded9321d7b2b94
SHA1(WiresharkPortable_3.2.8.paf.exe)=c0cd6b6e4e680dc7f4da5727b7158f75e4cfe851

Wireshark 3.2.8 Intel 64.dmg: 97737979 bytes
SHA256(Wireshark 3.2.8 Intel 64.dmg)=41e347c4c1f3a92214437d49ef0ac03ad06e176a30c232a488a997157424bf4b
RIPEMD160(Wireshark 3.2.8 Intel 64.dmg)=99b17dda5c0340dfe89c2f36bcbed4b81a60c8f8
SHA1(Wireshark 3.2.8 Intel 64.dmg)=88f8129a3efaf788a5a63d8ac304e9d3a1980671

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: OpenPGP_0x82244A78E6FEAEEA_and_old_rev.asc
Description: application/pgp-keys

Attachment: OpenPGP_signature
Description: OpenPGP digital signature