summaryrefslogtreecommitdiff
path: root/tests/test-commit-sign.sh
diff options
context:
space:
mode:
authorColin Walters <walters@verbum.org>2016-11-16 11:50:43 -0500
committerAtomic Bot <atomic-devel@projectatomic.io>2016-11-17 11:33:41 +0000
commit24bf257ee9f16959a6f480c7c1c16cdbe4aabc91 (patch)
tree9b3baf25f891883934d5732aaf07ab1104e200c3 /tests/test-commit-sign.sh
parentf244c702772c69378099685316033d4a6f7b862c (diff)
downloadostree-24bf257ee9f16959a6f480c7c1c16cdbe4aabc91.tar.gz
lib: Add an API to GPG verify a commit given a remote
Conceptually we've been moving towards having our GPG verification paths be per-remote. The code internally supports this, but we didn't expose an API to use it conveniently. This came up when trying to add a new `gpgkeypath` option, since right now rpm-ostree manually finds keyrings for the remote, and hence it wasn't looking at the keypath, and said "Unknown key" in status. Adding an API fixes this nicely. Closes: #576 Approved by: giuseppe
Diffstat (limited to 'tests/test-commit-sign.sh')
-rwxr-xr-xtests/test-commit-sign.sh2
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/test-commit-sign.sh b/tests/test-commit-sign.sh
index 01eb45f8..60265c1a 100755
--- a/tests/test-commit-sign.sh
+++ b/tests/test-commit-sign.sh
@@ -80,6 +80,8 @@ mkdir repo
${CMD_PREFIX} ostree --repo=repo init
${CMD_PREFIX} ostree --repo=repo remote add origin $(cat httpd-address)/ostree/gnomerepo
${CMD_PREFIX} ostree --repo=repo pull origin main
+${CMD_PREFIX} ostree --repo=repo show --gpg-verify-remote=origin main | grep -o 'Found [[:digit:]] signature' > show-verify-remote
+assert_file_has_content show-verify-remote 'Found 1 signature'
rm repo -rf
# A test with corrupted detached signature