summaryrefslogtreecommitdiff
path: root/src/libostree/ostree-sign-dummy.h
diff options
context:
space:
mode:
authorColin Walters <walters@verbum.org>2020-06-17 00:22:49 +0000
committerColin Walters <walters@verbum.org>2020-06-17 00:33:47 +0000
commit36258036ae1388c728eec0237b283e225f64a7b1 (patch)
tree1616ed7bc9d2e7ae0b946c01e894c0b5e39e65c2 /src/libostree/ostree-sign-dummy.h
parentb2dde24f00699822c27b4ab453a4340ddc3c2245 (diff)
downloadostree-36258036ae1388c728eec0237b283e225f64a7b1.tar.gz
signapi: Change API to also return a success message
This is the dual of https://github.com/ostreedev/ostree/pull/2129/commits/1f3c8c5b3de978f6e069c24938967f823cce7ee8 where we output more detail when signapi fails to validate. Extend the API to return a string for success, which we output to stdout. This will help the test suite *and* end users validate that the expected thing is happening. In order to make this cleaner, split the "verified commit" set in the pull code into GPG and signapi verified sets, and have the signapi verified set contain the verification string. We're not doing anything with the verification string in the pull code *yet* but I plan to add something like `ostree pull --verbose` which would finally print this.
Diffstat (limited to 'src/libostree/ostree-sign-dummy.h')
-rw-r--r--src/libostree/ostree-sign-dummy.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/libostree/ostree-sign-dummy.h b/src/libostree/ostree-sign-dummy.h
index c37bcdfa..bf5d63a1 100644
--- a/src/libostree/ostree-sign-dummy.h
+++ b/src/libostree/ostree-sign-dummy.h
@@ -63,6 +63,7 @@ gboolean ostree_sign_dummy_data (OstreeSign *self,
gboolean ostree_sign_dummy_data_verify (OstreeSign *self,
GBytes *data,
GVariant *signatures,
+ char **success_message,
GError **error);
const gchar * ostree_sign_dummy_metadata_key (OstreeSign *self);