From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: importing PGP keys
Date: Wed, 21 Jan 2015 21:36:54 +0800 [thread overview]
Message-ID: <87lhkwfe6h.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <861tmo1e14.fsf@informationelle-selbstbestimmung-im-internet.de>
Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:
> 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
Interesting, thanks for the link! But that doesn't look like it can tell
Gnus to use a certain key for certain contacts. I assume I'd need some
sort of BBDB-based thing to work well.
>> 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 think I was confused -- it's not that the key has no uid, but that
the uid is just a string of letters, not an email address. Not human
friendly, indeed! But I guess not actually a malformed public key. Still
makes it very hard to exchange encrypted emails.
>> 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.
Very good point!
prev parent reply other threads:[~2015-01-21 13:36 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
2015-01-21 13:36 ` Eric Abrahamsen [this message]
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=87lhkwfe6h.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).