From: Richard Stallman <rms@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 13551@debbugs.gnu.org
Subject: bug#13551: acknowledged by developer (control message for bug #13551)
Date: Fri, 27 Sep 2019 21:32:21 -0400 [thread overview]
Message-ID: <E1iE1av-0002jt-HP@fencepost.gnu.org> (raw)
In-Reply-To: <87pnjliuqh.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 27 Sep 2019 18:12:22 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I'm not sure I understand. I think it does do something completely
> predictable -- choose the key ring entry that matches what's in your
> "From" header.
We seem to be failing to commnuicate. My From header always says
"rms@gnu.org", but we're talking about the address I am sending to --
in the To field. Is that what you mean?
The behavior that you describe is totally unpredictable for me because
it depends on data I don't know, and have no other reason to know.
When foo@bar.com sends me a key, I don't notice what other addresses
that key covers. There is no reason to. And those alternate short
addresses are not listed by epa-list-keys.
If I have a key for 'arthur@gnu.org' and another for
'arthur@berkeley.edu', it is a nuisice for me to check which one, if
either, lists just 'arthur' as an address. Especially since when I
send mail to 'arthur@gnu.org' I may not even remember I know
'arthur@berkeley.edu'.
When I send mail to just 'arthur', that is equivalent by default to
'arthur@gnu.org'. I often omit '@gnu.org' knowing this.
Encryption should do the same thing: treat 'arthur' as short for
'arthur@gnu.org'. That way it will always encrypt for the person that
the mail is going to.
--
Dr Richard Stallman
Founder, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2019-09-28 1:32 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
[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 [this message]
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=E1iE1av-0002jt-HP@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=13551@debbugs.gnu.org \
--cc=larsi@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.
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).