Add a predicate to check whether we are in a given compliance mode, a
function that computes the minimum of the validity of all UIDs, and a
macro that can be used to check various objects for compliance with
CO_DE_VS without breaking compilation with older versions of GPGME,
and without cluttering the code with preprocessor conditionals.
Signed-off-by: Justus Winter <justus@gnupg.org>
Integrate compliance information in results if run in CO_DE_VS mode
When decrypting data and verifying signatures, inform the user about
whether or not the operation was VS-compliant if Kleopatra is run in
CO_DE_VS mode.
Signed-off-by: Justus Winter <justus@gnupg.org>
Display the new field 'Validity'
The key model recently gained a new field. Display this.
Signed-off-by: Justus Winter <justus@gnupg.org>
Display compliance information in the encryption wizard
Display whether or not a cryptographic operation will be in compliance
with CO_DE_VS by stating so in a label, coloring the 'next' button,
and adding an icon to it.
Signed-off-by: Justus Winter <justus@gnupg.org>
Add a convenient button to list keys that are not certified
Check if there are keys that are not fully certified, and if there
are, display a button next to the filter combobox that offers a quick
way to list those keys.
Signed-off-by: Justus Winter <justus@gnupg.org>
Here arc, butcher this commit...