On Mon, Jun 17, 2019 at 03:17:13PM +0000, Anders Broman wrote:
> Hi,
>
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the
> symbols file: see diff output below
>
> dpkg-gensymbols: warning: debian/libwsutil0/DEBIAN/symbols doesn't match
> completely debian/libwsutil0.symbols
>
> --- debian/libwsutil0.symbols (libwsutil0_3.1.0_amd64)
>
> +++ dpkg-gensymbolsasqzzn 2019-06-17 16:50:31.010999810 +0200
>
> @@ -50,8 +50,8 @@
>
> create_tempfile@Base 1.12.0~rc1
>
> create_timestamp@Base 2.5.0
>
> crypt_des_ecb@Base 2.3.0
>
> - crypto_scalarmult_curve25519@Base 2.9.0
>
> - crypto_scalarmult_curve25519_base@Base 2.9.0
>
> +#MISSING: 3.1.0# crypto_scalarmult_curve25519@Base 2.9.0
>
> +#MISSING: 3.1.0# crypto_scalarmult_curve25519_base@Base 2.9.0
>
> data_file_url@Base 2.3.0
>
> decrypt_xtea_ecb@Base 2.5.0
>
> decrypt_xtea_le_ecb@Base 2.5.0
>
>
>
> Do we need dummy versions if gcrypt is not of the right version? Why did it
> not fail before? No consumer until now?
This API is used by the WireGuard dissector (since Wireshark 3.0) and
requires Libgcrypt 1.7 which is not present in Ubuntu 16.04, Debian
Jessie and RHEL6/7. Debian Jessie is already EOL, ubuntu 16.04 is EOL in
April 2021 however.
Callers must check for the availability of an appropriate Libgcrypt
version before calling it. For simplicity, I have a slight preference
for not adding dummy versions, but if you think it is better to have it,
it could be done anyway?
--
Kind regards,
Peter Wu
https://lekensteyn.nl
