From: Russ Allbery <eagle@eyrie.org>
To: ding@gnus.org
Subject: Re: importing PGP keys
Date: Tue, 20 Jan 2015 22:29:10 -0800 [thread overview]
Message-ID: <87mw5csl3d.fsf@hope.eyrie.org> (raw)
In-Reply-To: <smuzj9dhgl6.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Tue, 20 Jan 2015 05:49:41 -0500")
Greg Troxel <gdt@lexort.com> writes:
> 1 and 3 are certainly useful code to share, but don't seem super tricky.
> I am curious what people are doing for 2. bbdb?
GnuPG does this itself using the email address published in the key ID,
and I normally just rely on that and don't retain keys in my personal
public keyring that violate my expectations there. (Admittedly, I'm not
great about checking this.)
Are you running across keys where the address at which you contact the
person isn't represented in the key IDs? Or are just not wanting to trust
the information GnuPG retains?
I think the default Gnus behavior is to use GnuPG to check for a key ID
matching the target email address.
--
Russ Allbery (eagle@eyrie.org) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2015-01-21 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 10:45 Eric Abrahamsen
2015-01-20 10:49 ` Greg Troxel
2015-01-21 6:29 ` Russ Allbery [this message]
2015-01-21 7:03 ` Eric Abrahamsen
2015-01-21 13:03 ` Jens Lechtenboerger
2015-01-21 13:36 ` Eric Abrahamsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mw5csl3d.fsf@hope.eyrie.org \
--to=eagle@eyrie.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).