From: Daiki Ueno <ueno@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Wherein I argue for the inclusion of libnettle in Emacs 24.5
Date: Wed, 05 Feb 2014 17:19:13 +0900 [thread overview]
Message-ID: <m3ha8ex98e.fsf-ueno@gnu.org> (raw)
In-Reply-To: <87y51qcace.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 05 Feb 2014 02:00:49 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> Please see my objection to loose coupling of encryption primitives in
> particular.
Didn't I post a link to the idea of this loose coupling? It is mainly
for security reasons. For example, there's usually a limit of secure
memory and it makes sense to do all the secret key operation in a
minimal core (gpg-agent) to utilize it.
I don't think you can provide the same level of security using
encryption primitives within Emacs.
> Right. Shelling out to an external binary every time you want to verify
> a package's signature or want to encrypt/decrypt/sign data makes perfect
> sense.
At least it works at acceptable performance now.
> Blindly entering your passphrase in an anonymous popup that says it's
> from the GnuPG agent is how things are done.
This could be fixed. Sounds definitely easier than importing plenty of
crypto primitives from a C library.
> Trusting loosely coupled components is standard industry practice.
See above.
> Forcing users to do all of that, or "no encryption for you" is for their
> own good, on every platform where Emacs runs, from Android to W32 to Mac
> OS X to many flavors of Unix. Users are just too stupid to decide these
> things on their own.
I don't get it. Are there any platforms where Emacs work, while GPG
does not?
> Is that how experts with a crypto/security background do it? I'm
> understanding now.
Better than letting you write encryption code for me.
Case study (sorry Jose):
https://lists.gnu.org/archive/html/bug-recutils/2012-04/msg00001.html
I can easily imagine you will make similar (or more serious) mistakes
here and there, once crypto primitives are available.
--
Daiki Ueno
next prev parent reply other threads:[~2014-02-05 8:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 22:36 Wherein I argue for the inclusion of libnettle in Emacs 24.5 Lars Ingebrigtsen
2014-02-04 3:21 ` Stefan Monnier
2014-02-04 13:07 ` Ted Zlatanov
2014-02-04 14:44 ` Stephen J. Turnbull
2014-02-04 18:36 ` Ted Zlatanov
2014-02-04 22:44 ` Lars Ingebrigtsen
2014-02-05 2:28 ` Stefan Monnier
2014-02-05 2:39 ` Lars Ingebrigtsen
2014-02-05 7:00 ` Ted Zlatanov
2014-02-05 8:13 ` Stephen J. Turnbull
2014-02-05 13:41 ` Ted Zlatanov
2014-02-05 15:50 ` andres.ramirez
2014-02-05 17:00 ` chad
2014-02-05 18:55 ` Ted Zlatanov
2014-02-06 5:03 ` Stephen J. Turnbull
2014-02-06 11:49 ` Ted Zlatanov
2014-02-06 13:03 ` Stefan Monnier
2014-02-06 14:28 ` Ted Zlatanov
2014-02-06 15:05 ` Stephen J. Turnbull
2014-02-06 15:54 ` Ted Zlatanov
2014-02-07 2:06 ` Stephen J. Turnbull
2014-02-07 6:51 ` David Kastrup
2014-02-07 7:15 ` Stephen J. Turnbull
2014-02-07 8:53 ` David Kastrup
2014-02-07 10:00 ` Stephen J. Turnbull
2014-02-07 10:49 ` David Kastrup
2014-02-07 20:43 ` Stephen J. Turnbull
2014-02-07 21:42 ` Ted Zlatanov
2014-02-07 22:23 ` Stephen J. Turnbull
2014-02-07 15:30 ` Ted Zlatanov
2014-02-07 9:07 ` Daiki Ueno
2014-02-07 11:54 ` Ted Zlatanov
2014-02-08 8:11 ` Daiki Ueno
2014-02-08 16:59 ` Ted Zlatanov
2014-02-05 8:19 ` Daiki Ueno [this message]
2014-02-04 13:10 ` Ted Zlatanov
2014-02-04 16:27 ` Paul Eggert
2014-02-04 18:32 ` Ted Zlatanov
2014-02-04 19:04 ` Paul Eggert
2014-02-04 20:11 ` Ted Zlatanov
2014-02-04 21:46 ` Paul Eggert
2014-02-04 22:44 ` Ted Zlatanov
2014-02-04 22:36 ` Lars Ingebrigtsen
2014-02-05 5:11 ` Daiki Ueno
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=m3ha8ex98e.fsf-ueno@gnu.org \
--to=ueno@gnu.org \
--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.