ostree/tests/gpg-verify-data/README.md

This is a GPG config directory for use with the OstreeGpgVerifyResult
test cases. The test data (`lgpl2`) is signed with a variety of valid
and invalid GPG keys in a detached signature file (`lgpl2.sig`). In
addition, each detached signature is available in a separate file
(`lgpgl2.sig<N>`).

The passphrase for all the keys is `redhat`.
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). 2015-03-04 12:44:47 -05:00			`This is a GPG config directory for use with the OstreeGpgVerifyResult`
tests/gpg-verify-data: Split out signature data The full block with all 5 signatures remains, but this allows passing individual signatures through the GPG verification APIs. The split was done with `gpgsplit`, and looking at the output of `gpg --list-packets` of the split and unsplit files appears correct. 2019-06-19 16:31:18 -05:00			test cases. The test data (`lgpl2`) is signed with a variety of valid
			and invalid GPG keys in a detached signature file (`lgpl2.sig`). In
			`addition, each detached signature is available in a separate file`
			(`lgpgl2.sig<N>`).
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). 2015-03-04 12:44:47 -05:00
			The passphrase for all the keys is `redhat`.