Package: rnetclient Version: 2017.1-1+b2 Followup-For: Bug #1009398 This is caused by libgcrypt working under FIPS mode by default, unless its global_init has been called. That requires gcry_check_version to be called, as one of the possibilities.
Here is an attached debpatch. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-11-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rnetclient depends on: ii libc6 2.33-7 ii libgcrypt20 1.10.1-2 ii libgnutls30 3.7.4-2 ii zlib1g 1:1.2.11.dfsg-4 rnetclient recommends no packages. rnetclient suggests no packages. -- no debconf information
Index: rnetclient-2017.1/decfile.c =================================================================== --- rnetclient-2017.1.orig/decfile.c +++ rnetclient-2017.1/decfile.c @@ -489,6 +489,7 @@ char * rnet_decfile_get_file_hash(struct { char *hash; size_t len; + gcry_check_version(NULL); if (gcry_md_test_algo(GCRY_MD_MD5)) return NULL; len = gcry_md_get_algo_dlen(GCRY_MD_MD5);