summaryrefslogtreecommitdiff
path: root/src/libostree/ostree-gpg-verify-result.c
diff options
context:
space:
mode:
authorMatthew Barnes <mbarnes@redhat.com>2015-03-19 10:21:08 -0400
committerMatthew Barnes <mbarnes@redhat.com>2015-03-19 10:21:08 -0400
commitf9e95e2cd39e23b2c420addc10917e8e3d6b7a20 (patch)
tree47a4e6e2d73b2c0dbb3138f9ba0831e19f8fa6c0 /src/libostree/ostree-gpg-verify-result.c
parent9b8bad3c2ee183a409d14d56a45a501e68a5ef44 (diff)
downloadostree-f9e95e2cd39e23b2c420addc10917e8e3d6b7a20.tar.gz
gpg: Link to GPGME bug about GPGME_SIGSUM_KEY_REVOKED
Diffstat (limited to 'src/libostree/ostree-gpg-verify-result.c')
-rw-r--r--src/libostree/ostree-gpg-verify-result.c5
1 files changed, 4 insertions, 1 deletions
diff --git a/src/libostree/ostree-gpg-verify-result.c b/src/libostree/ostree-gpg-verify-result.c
index 301ff912..7f4b3d83 100644
--- a/src/libostree/ostree-gpg-verify-result.c
+++ b/src/libostree/ostree-gpg-verify-result.c
@@ -97,7 +97,10 @@ signing_key_is_revoked (gpgme_signature_t signature)
* bit on a revoked signing key but rather GPGME_SIGSUM_SYS_ERROR and the
* status field shows GPG_ERR_CERT_REVOKED. Turns out GPGME is expecting
* GPG_ERR_CERT_REVOKED in the validity_reason field which would then set
- * the summary bit. Unsure if this is a bug, but best check for both. */
+ * the summary bit.
+ *
+ * Reported to GPGME: https://bugs.g10code.com/gnupg/issue1929
+ */
return (signature->summary & GPGME_SIGSUM_KEY_REVOKED) ||
((signature->summary & GPGME_SIGSUM_SYS_ERROR) &&