gpg: Add OstreeGpgVerifyResult
Wrappers a referenced gpgme_verify_result_t so detailed verify results can be examined independently of executing a verify operation. _ostree_gpg_verifier_check_signature() now returns this object instead of a single valid/invalid boolean, but the idea is for OstreeRepo to also return this object for commit signature verification so it can be utilized at the CLI layer (and possibly by other programs).
This commit is contained in:
1 parent
553d7840d5
commit
4a2733f9e7
19 files changed
+1679
-105
No files matched your search
@@ -75,6 +75,7 @@ IGNORE_HFILES= \
|
||||
ostree-core-private.h \
|
||||
ostree-fetcher.h \
|
||||
ostree-gpg-verifier.h \
|
||||
ostree-gpg-verify-result-private.h \
|
||||
ostree-kernel-args.h \
|
||||
ostree-libarchive-input-stream.h \
|
||||
ostree-lzma-compressor.h \
|
||||
|
||||
@@ -26,6 +26,7 @@
|
||||
<xi:include href="xml/libostree-async-progress.xml"/>
|
||||
<xi:include href="xml/libostree-sepolicy.xml"/>
|
||||
<xi:include href="xml/libostree-sysroot-upgrader.xml"/>
|
||||
<xi:include href="xml/libostree-gpg-verify-result.xml"/>
|
||||
<xi:include href="xml/libostree-bootconfig-parser.xml"/>
|
||||
<xi:include href="xml/libostree-chain-input-stream.xml"/>
|
||||
<xi:include href="xml/libostree-checksum-input-stream.xml"/>
|
||||
|
||||
@@ -165,6 +165,22 @@ ostree_diff_print
|
||||
ostree_diff_item_get_type
|
||||
</SECTION>
|
||||
|
||||
<SECTION>
|
||||
<FILE>libostree-gpg-verify-result</FILE>
|
||||
OstreeGpgVerifyResult
|
||||
OstreeGpgSignatureAttr
|
||||
ostree_gpg_verify_result_count_all
|
||||
ostree_gpg_verify_result_count_valid
|
||||
ostree_gpg_verify_result_lookup
|
||||
ostree_gpg_verify_result_get
|
||||
ostree_gpg_verify_result_get_all
|
||||
<SUBSECTION Standard>
|
||||
OSTREE_GPG_VERIFY_RESULT
|
||||
OSTREE_IS_GPG_VERIFY_RESULT
|
||||
OSTREE_TYPE_GPG_VERIFY_RESULT
|
||||
ostree_gpg_verify_result_get_type
|
||||
</SECTION>
|
||||
|
||||
<SECTION>
|
||||
<FILE>libostree-mutable-tree</FILE>
|
||||
OstreeMutableTree
|
||||
|
||||
Reference in new issue
Block a user