doc: Fix, update, add API documentation

--
Nowadays, VS-NfD requires RSA 3072. And the documentation of
gpgme_signature_t was missing the compliance flags.
This commit is contained in:
Ingo Klöcker 2024-10-21 14:23:44 +02:00
parent 227c9c763b
commit f510c5d78c
No known key found for this signature in database
GPG Key ID: F5A5D1692277A1E9

View File

@ -3642,10 +3642,10 @@ according to local government regulations.
This is true if the subkey complies with the rules for classified
information in Germany at the restricted level (VS-NfD). This are
currently RSA keys of at least 2048 bits or ECDH/ECDSA keys using a
currently RSA keys of at least 3072 bits or ECDH/ECDSA keys using a
Brainpool curve.
@item unsigned int beta_complinance : 1;
@item unsigned int beta_compliance : 1;
@since{1.24.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.
@ -5905,7 +5905,7 @@ The message claims that the content is a MIME object.
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_complinance : 1;
@item unsigned int beta_compliance : 1;
@since{1.24.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.
@ -6278,6 +6278,15 @@ of the issuing certificate. In contrast the default validation model
checks the validity of signature as well at the entire certificate chain
at the current time.
@item unsigned int is_de_vs : 1;
@since{1.10.0}
The signature was created in a VS-NfD compliant way. This is a
specification in Germany for a restricted communication level.
@item unsigned int beta_compliance : 1;
@since{1.24.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.
@item gpgme_validity_t validity
The validity of the signature.