diff options
| author | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2019-05-04 17:33:28 -0400 |
|---|---|---|
| committer | David Bremner <david@tethera.net> | 2019-05-07 06:42:21 -0300 |
| commit | 7d48604157477054624d010fca496f7eb0d1168b (patch) | |
| tree | 26d814c0953817aaa69f8ab50663e4a208adee16 /bindings/python/docs/source/query.rst | |
| parent | 93e699e5c86bb93b2992f4ab3a15680824b7ee2d (diff) | |
test/crypto: add_gnupg_home should have ultimate trust on "its own" key
The typical use case for gpg is that if you control a secret key, you
mark it with "ultimate" ownertrust.
The opaque --import-ownertrust mechanism is GnuPG's standard mechanism
to set up ultimate ownertrust (the ":6:" means "ultimate", for
whatever reason).
We adjust the test suite to match this change, inverting the sense of
one test: since the default is now that the user ID of the suite's own
key is valid, we change the test to make sure that the user ID is not
emitted when it is *not* valid.
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Diffstat (limited to 'bindings/python/docs/source/query.rst')
0 files changed, 0 insertions, 0 deletions