From: Robert Pluim <rpluim@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Autocrypt header field
Date: Wed, 21 Feb 2018 11:19:54 +0100 [thread overview]
Message-ID: <87y3jmfxv9.fsf@gmail.com> (raw)
In-Reply-To: <E1eoRDO-0006We-NO@fencepost.gnu.org> (Richard Stallman's message of "Wed, 21 Feb 2018 05:01:30 -0500")
Richard Stallman <rms@gnu.org> writes:
> [[[ 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. ]]]
>
> > What level of support were you thinking of? The Autocrypt
> > recommendations include a whole bunch of PGP key generation and setup
> > messaging that I'm not convinced are necessary.
>
> We should consult an expert such as Werner Koch about that.
I was unclear: Autocrypt has a setup procedure that involves
generating a new PGP key specifically for use with it, and producing a
setup email message containing that key. Many users will probably
already have a PGP key that they would prefer to use instead,
obviating the need for such setup.
> Snarfing the key from
> > the header and adding it to the user's keyring should be easy enough. [1]
>
> I suppose that is the job to be done; you've raised the question of how
> to do that right.
>
That's part of what needs to be done. Once the keys are stored
somewhere, a decision then needs to be made on a per-message basis as
to whether or not to sign/encrypt, the keys need to be kept track of
in case they change, and probably more (I haven't committed the
Autocrypt specification to memory)
> > [1] Or should this go to a separate Autocrypt keyring?
>
> I never heard of Autocrypt before. What would be the reason for doing
> that?
It's a whole new method for automatically signing email. People might
not want emacs to start adding keys to their default keyring
automatically. In the only other similar case I know of, namely elpa
package signature checking, a separate keyring is created.
Robert
next prev parent reply other threads:[~2018-02-21 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 22:17 Autocrypt header field Richard Stallman
2018-02-20 11:42 ` Robert Pluim
2018-02-21 10:01 ` Richard Stallman
2018-02-21 10:19 ` Robert Pluim [this message]
2018-02-23 23:52 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3jmfxv9.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.