From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] test: add_gnupg_home should have ultimate trust on "its own" key
Date: Wed, 24 Apr 2019 18:13:31 -0400 [thread overview]
Message-ID: <87ftq7rr04.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20190424220644.23775-1-dkg@fifthhorseman.net>
[-- 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 --]
next prev parent reply other threads:[~2019-04-24 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 22:06 [PATCH] test: add_gnupg_home should have ultimate trust on "its own" key Daniel Kahn Gillmor
2019-04-24 22:13 ` Daniel Kahn Gillmor [this message]
2019-04-24 22:15 ` [PATCH v2] " Daniel Kahn Gillmor
2019-04-24 23:23 ` [PATCH v3] " Daniel Kahn Gillmor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftq7rr04.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).