Wireshark mailing list archives
Re: Can the legacy HAVE_LIBGCRYPT_AEAD check be removed?
From: "Dr. Matthias St. Pierre" <Matthias.St.Pierre () ncp-e com>
Date: Mon, 12 Jul 2021 19:40:15 +0000
If some changes were done to fix the compilation, it means that some people still use a libgcrypt version older than 1.6.0. And as seen in our CMakeLists.txt file, the minimum version required for now is 1.5.0.
I understand your reluctancy to upgrade the requirements, but don’t you think that ten years is a *very long* time to support an old cryptographic library (libgcrypt 1.5.0 was released in 2011-06-29), just because somebody out there might still be using it? Matthias
Attachment:
smime.p7s
Description:
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Can the legacy HAVE_LIBGCRYPT_AEAD check be removed? Dr. Matthias St. Pierre (Jul 12)
- Re: Can the legacy HAVE_LIBGCRYPT_AEAD check be removed? Pascal Quantin (Jul 12)
- Re: Can the legacy HAVE_LIBGCRYPT_AEAD check be removed? John Thacker (Jul 12)
- Re: Can the legacy HAVE_LIBGCRYPT_AEAD check be removed? Dr. Matthias St. Pierre (Jul 12)
- Re: Can the legacy HAVE_LIBGCRYPT_AEAD check be removed? Joakim (Jul 18)
- Re: Can the legacy HAVE_LIBGCRYPT_AEAD check be removed? Dr. Matthias St. Pierre (Jul 19)
- Re: Can the legacy HAVE_LIBGCRYPT_AEAD check be removed? John Thacker (Jul 12)
- Re: Can the legacy HAVE_LIBGCRYPT_AEAD check be removed? Pascal Quantin (Jul 12)
- Re: Can the legacy HAVE_LIBGCRYPT_AEAD check be removed? Dr. Matthias St. Pierre (Jul 12)