From 2100e1fbdfeb9ecda00787032a8256938a113dde Mon Sep 17 00:00:00 2001 From: Ingo Klöcker Date: Tue, 21 Apr 2026 10:46:17 +0200 Subject: Add flag fields is_de_vs and beta_compliance to encryption results * src/encrypt.c (_gpgme_encrypt_status_handler): Handle the compliance status line. * src/gpgme.h.in (struct _gpgme_op_encrypt_result): Add fields is_de_vs and beta_compliance. (gpgme_status_code_t): Add status code for the encryption compliance status line. * src/status-table.c (status_table): Add encryption compliance status line. * tests/run-encrypt.c (print_encrypt_result): Print compliance. -- This allows checking whether the encrypt operation is in compliance with the VS-NfD criteria. GnuPG-bug-id: 6702 --- doc/gpgme.texi | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'doc') diff --git a/doc/gpgme.texi b/doc/gpgme.texi index f9bcb7d6..5acefe24 100644 --- a/doc/gpgme.texi +++ b/doc/gpgme.texi @@ -7065,6 +7065,16 @@ members: @item gpgme_invalid_key_t invalid_recipients A linked list with information about all invalid keys for which the data could not be encrypted. + +@item unsigned int is_de_vs : 1; +@since{2.1.0} +The message was encrypted in a VS-NfD compliant way. This is a +specification in Germany for a restricted communication level. + +@item unsigned int beta_compliance : 1; +@since{2.1.0} +The compliance flags (e.g. is_de_vs) are set but the software has not +yet been approved or is in a beta state. @end table @end deftp -- cgit