Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@lexort.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: importing PGP keys
Date: Tue, 20 Jan 2015 05:49:41 -0500	[thread overview]
Message-ID: <smuzj9dhgl6.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <87d269ohlm.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 20 Jan 2015 18:45:57 +0800")

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


Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> So someone just emailed me their public PGP key. I can save the MIME
> attachment to a file, then call "gpg --import thekey.key", but the
> resulting key isn't associated with their email address, and therefore
> I'm not able to send them encrypted emails, at least not by default.
>
> Does anyone have a clever function for importing an attached key and
> automatically associating it with the email address which sent it? Or
> somehow doing it after the fact? I've been googling for a while now, and
> haven't found the answer...

There are three separate issues lurking here:

  1) getting the key to gpg --import
  2) how to record an email address -> pubkey mapping
  3) how to do (2) automatically

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?

Also, are you using epg?  It seems that is the preferred way (over pgg)
these days, and it's what I use.

[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]

  reply	other threads:[~2015-01-20 10:49 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 [this message]
2015-01-21  6:29   ` Russ Allbery
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=smuzj9dhgl6.fsf@linuxpal.mit.edu \
    --to=gdt@lexort.com \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    /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).