From 90c514868ff5fcf6d39490d4874ac3a31ba9e85f Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Thu, 28 Jan 2021 15:48:08 +0100 Subject: Include the library version in the compliance checks. * common/compliance.c (gnupg_gcrypt_is_compliant): New. (gnupg_rng_is_compliant): Also check library version. * g10/mainproc.c (proc_encrypted): Use new function. (check_sig_and_print): Ditto. * sm/decrypt.c (gpgsm_decrypt): Ditto. * sm/encrypt.c (gpgsm_encrypt): Ditto. * sm/verify.c (gpgsm_verify): Ditto -- This will eventually allow us to declare Libgcrypt 1.9 to be de-vs compliant. GnuPG can use this information then for its own checks. As of now GnuPG tests the version of the used library but that is a bit cumbersome to maintain. Signed-off-by: Werner Koch --- sm/encrypt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'sm/encrypt.c') diff --git a/sm/encrypt.c b/sm/encrypt.c index 34a5e878b..fbd88b6cd 100644 --- a/sm/encrypt.c +++ b/sm/encrypt.c @@ -807,7 +807,7 @@ gpgsm_encrypt (ctrl_t ctrl, certlist_t recplist, int data_fd, estream_t out_fp) } } - if (compliant) + if (compliant && gnupg_gcrypt_is_compliant (CO_DE_VS)) gpgsm_status (ctrl, STATUS_ENCRYPTION_COMPLIANCE_MODE, gnupg_status_compliance_flag (CO_DE_VS)); -- cgit v1.2.3