ostree/tests/gpg-verify-data
Matthew Barnes da918a74d5 gpg: Regenerate test data for test-gpg-verify-result
Turns out the expired signature case was failing because the signature
itself was corrupted.  Reconstructed the test data and updated the test
code.  Note, an expired signature is still counted as valid.

Also, handy debugging trick for setting a key or signature expiry: the
CLI makes it appear the shortest expiry is 1 day, but it also secretly
recognizes "seconds=N".
2015-03-19 12:43:04 -04:00
..
gpg.conf gpg: Add OstreeGpgVerifyResult 2015-03-18 11:52:22 -04:00
lgpl2 gpg: Add OstreeGpgVerifyResult 2015-03-18 11:52:22 -04:00
lgpl2.sig gpg: Regenerate test data for test-gpg-verify-result 2015-03-19 12:43:04 -04:00
pubring.gpg gpg: Regenerate test data for test-gpg-verify-result 2015-03-19 12:43:04 -04:00
README.md gpg: Add OstreeGpgVerifyResult 2015-03-18 11:52:22 -04:00
secring.gpg gpg: Regenerate test data for test-gpg-verify-result 2015-03-19 12:43:04 -04:00
trustdb.gpg gpg: Regenerate test data for test-gpg-verify-result 2015-03-19 12:43:04 -04:00

This is a GPG config directory for use with the OstreeGpgVerifyResult test cases. The test data (lgplv2) is signed with a variety of valid and invalid GPG keys in a detached signature file (lgplv2.sig).

The passphrase for all the keys is redhat.