ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Can the legacy HAVE_LIBGCRYPT_AEAD check be removed?

From: "Dr. Matthias St. Pierre" <Matthias.St.Pierre@xxxxxxxxx>
Date: Mon, 12 Jul 2021 19:43:16 +0000
> The minimum version being stuck at 1.5.0 is, I believe, almost entirely due to RHEL/CentOS 7 being stuck at 1.5.3
> (https://gitlab.com/wireshark/wireshark/-/wikis/Development/Support_library_version_tracking#libgcrypt)

> It's a widely used enough distribution, still scheduled for 3 more years of support, that I think that for now the current approach of supporting it is reasonable. We do warn about it in strong terms.
> (The RH package may have some backports of features from later versions, but I haven't looked into it.)

> If at some point we want to drop RHEL 7 (and in a similar fashion, SUSE Enterprise Server 12), there's a number of packages whose version could be bumped, as seen on that page.

> John Thacker


Thanks for your reply, which crossed mine. Well, if it's still widely used by RHEL/CentOS 7, then there is nothing I can do about it at the moment.

Matthias

Attachment: smime.p7s
Description: S/MIME cryptographic signature