From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Stallman <rms@gnu.org>
Cc: 13551@debbugs.gnu.org
Subject: bug#13551: 24.3.50; epa-mail-encrypt chooses wrong key
Date: Mon, 23 Sep 2019 18:40:49 +0200 [thread overview]
Message-ID: <87lfuf0xv2.fsf@gnus.org> (raw)
In-Reply-To: <E1Tyqsx-0005dB-R9@fencepost.gnu.org> (Richard Stallman's message of "Fri, 25 Jan 2013 16:32:31 -0500")
Richard Stallman <rms@gnu.org> writes:
> I have a public key for martin@gnu.org and a key for another martin at
> another host. When I encrypt a message to `martin' -- which means, in
> my case, `martin@gnu.org' -- epa-mail-encrypt picks the other martin.
>
> epa needs to know the default mail hostname so as to pick the correct
> Martin. It can get that from the value of user-mail-address, and
> maybe have other ways to specify it.
I don't think any security-related software should be guessing based on
incomplete email addresses. As far as I can tell, it requires a
complete match, which I guess means you have a key for "martin" (without
a domain name) in your key ring.
Choosing this is the right thing to do, I think, so I'm closing this bug
report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-23 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k19z0xut.fsf@gnus.org>
2013-01-25 21:32 ` bug#13551: 24.3.50; epa-mail-encrypt chooses wrong key Richard Stallman
2019-09-23 16:40 ` Lars Ingebrigtsen [this message]
[not found] ` <handler.13551.C.156925686512740.notifdonectrl.0@debbugs.gnu.org>
2019-09-27 11:05 ` bug#13551: acknowledged by developer (control message for bug #13551) Richard Stallman
2019-09-27 16:12 ` Lars Ingebrigtsen
2019-09-28 1:32 ` Richard Stallman
2019-09-28 19:47 ` Lars Ingebrigtsen
2019-10-05 13:18 ` Richard Stallman
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfuf0xv2.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=13551@debbugs.gnu.org \
--cc=rms@gnu.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://git.savannah.gnu.org/cgit/emacs.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).