From: Tim Cross <theophilusx@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Autocrypt support
Date: Mon, 28 Aug 2017 22:47:29 +1000 [thread overview]
Message-ID: <CAC=50j-gP9hoUuU5AhMzYyLLTaH3YOc1OyTFQasyGiRwYjDajg@mail.gmail.com> (raw)
In-Reply-To: <87pobgf2qw.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2280 bytes --]
I agree. This spec looks very under developed yet and I'm not sure it
actually addresses the key issue which prevents more universal adoption of
end-to-end encrypted email.
The problem is and remains one of key management and humans, which becomes
even more difficult because it is trying to retro-fit encryption to a
protocol which has no support for it.
The real challenge for specs like this is that they mean nothing unless a
majority of mail clients support them. Getting them added is going to be
extremely difficult - near impossible. It is more likely we will just see
people move to different comms channels which are secure rather than trying
to retro fit traditional email. A bigger problem is that their spec for
level 1 only deals with users using a single mail client. I'm not sure in
this day of multiple devices this will be sufficient. The reason I moved to
an imap based setup is that I regularly use 3+ different mail clients on 4+
different devices. I need to be able to access my email from all of these
devices and this spec will fail to provide that. Level 2 looks like where
this functionality will be targeted. However, the problem is that level 1
may not get the uptake/momentum needed to get to level 2.
Note that I'm not meaning to disparage the effort - it is a good/meaningful
effort. However, I think it needs to mature a fair bit before any real
implementation/support can be added to existing mail clients. It is likely
efforts like this are what is needed to work out a better solution, but
this spec so far seems to lack some meat. It needs to provide more detail
on exactly what the key problems are which prevent automatic end-to-end
encryption of email and how this spec will address those problems.
Tim
On 28 August 2017 at 19:41, Robert Pluim <rpluim@gmail.com> wrote:
> Rajeev Narang <rajeevn@riseup.net> writes:
>
> > Is anyone working on supporting Autocrypt in emacs.
> >
> > https://autocrypt.org/en/latest/level1.html
> >
>
> I don't think so. I didn't see any rationale on that page for why we
> need yet another way of transferring keys and specifying encryption
> options in email headers, perhaps you could explain why Autocrypt
> would be a good thing?
>
> Regards
>
> Robert
>
>
>
--
regards,
Tim
--
Tim Cross
[-- Attachment #2: Type: text/html, Size: 3215 bytes --]
prev parent reply other threads:[~2017-08-28 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 21:27 Autocrypt support Rajeev Narang
2017-08-28 9:41 ` Robert Pluim
2017-08-28 12:47 ` Tim Cross [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='CAC=50j-gP9hoUuU5AhMzYyLLTaH3YOc1OyTFQasyGiRwYjDajg@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=emacs-devel@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.