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

[Joakim <oakimk@xxxxxxxxx>]

Hi,

yep, RHEL7 is still widely used, sadly :/
I have been correcting this ifdef a couple of times now.. https://gitlab.com/wireshark/wireshark/-/commits/master?search=LIBGCRYPT_AEAD

This since my dev env has not yet seen the light of RHEL8 

//Joakim

On Mon, 12 Jul 2021 at 19:43, Dr. Matthias St. Pierre <Matthias.St.Pierre@xxxxxxxxx> wrote:

> 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

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