[PATCH] test: add_gnupg_home should have ultimate trust on "its own" key

[PATCH] test: add_gnupg_home should have ultimate trust on "its own" key

[Daniel Kahn Gillmor]

The typical use case for gpg is that if you control a secret key, you
mark it with "ultimate" ownertrust.

This bizarrely opaque --import-ownertrust mechanism is GnuPG's
standard mechanism to set up ultimate ownertrust (the ":6" means
"ultimate", for whatever reason).
---
 test/test-lib.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/test/test-lib.sh b/test/test-lib.sh
index 58909ee7..6e383c85 100644
--- a/test/test-lib.sh
+++ b/test/test-lib.sh
@@ -120,6 +120,7 @@ add_gnupg_home ()
 
     # Change this if we ship a new test key
     FINGERPRINT="5AEAB11F5E33DCE875DDB75B6D92612D94E46381"
+    printf '%s:6\n' "$FINGERPRINT" | gpg --import-trustdb
 }
 
 # Each test should start with something like this, after copyright notices:
-- 
2.20.1

Re: [PATCH] test: add_gnupg_home should have ultimate trust on "its own" key

[Daniel Kahn Gillmor]

[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

On Wed 2019-04-24 18:06:44 -0400, Daniel Kahn Gillmor wrote:
> The typical use case for gpg is that if you control a secret key, you
> mark it with "ultimate" ownertrust.
>
> This bizarrely opaque --import-ownertrust mechanism is GnuPG's
> standard mechanism to set up ultimate ownertrust (the ":6" means
> "ultimate", for whatever reason).
> ---
>  test/test-lib.sh | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/test/test-lib.sh b/test/test-lib.sh
> index 58909ee7..6e383c85 100644
> --- a/test/test-lib.sh
> +++ b/test/test-lib.sh
> @@ -120,6 +120,7 @@ add_gnupg_home ()
>  
>      # Change this if we ship a new test key
>      FINGERPRINT="5AEAB11F5E33DCE875DDB75B6D92612D94E46381"
> +    printf '%s:6\n' "$FINGERPRINT" | gpg --import-trustdb

sigh.  this should of course be "--import-ownertrust", not
"--import-trustdb".  i'll send a fixed patch shortly.  Sorry for the
noise.

       --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

[PATCH v2] test: add_gnupg_home should have ultimate trust on "its own" key

[Daniel Kahn Gillmor]

The typical use case for gpg is that if you control a secret key, you
mark it with "ultimate" ownertrust.

This bizarrely opaque --import-ownertrust mechanism is GnuPG's
standard mechanism to set up ultimate ownertrust (the ":6" means
"ultimate", for whatever reason).
---
 test/test-lib.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/test/test-lib.sh b/test/test-lib.sh
index 70d7dcfe..89f84bbe 100644
--- a/test/test-lib.sh
+++ b/test/test-lib.sh
@@ -120,6 +120,7 @@ add_gnupg_home ()
 
     # Change this if we ship a new test key
     FINGERPRINT="5AEAB11F5E33DCE875DDB75B6D92612D94E46381"
+    printf '%s:6\n' "$FINGERPRINT" | gpg --import-ownertrust
 }
 
 # Each test should start with something like this, after copyright notices:
-- 
2.20.1

[PATCH v3] test: add_gnupg_home should have ultimate trust on "its own" key

[Daniel Kahn Gillmor]

The typical use case for gpg is that if you control a secret key, you
mark it with "ultimate" ownertrust.

This bizarrely opaque --import-ownertrust mechanism is GnuPG's
standard mechanism to set up ultimate ownertrust (the ":6" means
"ultimate", for whatever reason).
---
 test/test-lib.sh | 1 +
 1 file changed, 1 insertion(+)

This differs from v2 in that it adds the --quiet flag, so that the
tests don't have noisy output like "gpg: inserting ownertrust of 6"


diff --git a/test/test-lib.sh b/test/test-lib.sh
index 70d7dcfe..db3ffd8d 100644
--- a/test/test-lib.sh
+++ b/test/test-lib.sh
@@ -120,6 +120,7 @@ add_gnupg_home ()
 
     # Change this if we ship a new test key
     FINGERPRINT="5AEAB11F5E33DCE875DDB75B6D92612D94E46381"
+    printf '%s:6\n' "$FINGERPRINT" | gpg --quiet --import-ownertrust
 }
 
 # Each test should start with something like this, after copyright notices:
-- 
2.20.1