From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: importing PGP keys
Date: Wed, 21 Jan 2015 14:03:51 +0100 [thread overview]
Message-ID: <861tmo1e14.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <877fwghaz5.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 21 Jan 2015 15:03:10 +0800")
On 2015-01-21, Eric Abrahamsen wrote:
> Russ Allbery <eagle@eyrie.org> writes:
>
>> 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?
I’m using jl-encrypt ;)
http://www.emacswiki.org/emacs/DefaultEncrypt
> In my case, the problem was that the person just sent me the raw public
> key block;
I’m surprised that this is possible. How, actually?
You might want to warn him/her not to do this.
Without uid, you must remember the key fingerprint if you want to
use the key. This does not appear to be human friendly. Moreover,
as any link between key and e-mail address is missing, e-mail
software cannot offer automatic encryption.
> I was sure that the gpg key management interface would provide some way
> of manually adding an email address to someone else's public key, but
> I'm not finding it...
An owner of the secret key can use the gpg command adduid.
You must not be able to add uids to other people’s keys. Otherwise,
you could redirect e-mails encrypted to them.
Best wishes
Jens
next prev parent reply other threads:[~2015-01-21 13:03 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
2015-01-21 7:03 ` Eric Abrahamsen
2015-01-21 13:03 ` Jens Lechtenboerger [this message]
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=861tmo1e14.fsf@informationelle-selbstbestimmung-im-internet.de \
--to=jens.lechtenboerger@fsfe.org \
--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).