From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Wherein I argue for the inclusion of libnettle in Emacs 24.5
Date: Sat, 08 Feb 2014 11:59:55 -0500 [thread overview]
Message-ID: <87wqh5a6b8.fsf@lifelogs.com> (raw)
In-Reply-To: 87vbwqm3b6.fsf-ueno@gnu.org
On Sat, 08 Feb 2014 17:11:41 +0900 Daiki Ueno <ueno@gnu.org> wrote:
DU> Ted Zlatanov <tzz@lifelogs.com> writes:
>> design, is hard to use securely as an API. As proof, consider the Java
>> libraries to implement OpenPGP internally (BouncyCastle). Similar
>> situation in Go (http://godoc.org/code.google.com/p/go.crypto/openpgp).
>>
>> Is Emacs so different from those platforms, given applications like Gnus
>> and Magit and eww?
DU> Isn't it because those platforms provide more advanced memory management
DU> mechanisms than Emacs?
I think it's for more practical reasons, like "we don't want to force
our user base to use GnuPG because it doesn't work for everyone."
That's my guess.
DU> I was talking about the risk of keeping passwords in Emacs memory
DU> for a long time, as string copy also happens in GC.
OK.
>> I feel that, unless we wish to blame the user for not locking their
>> desktop, Emacs should at least try to protect such passwords in its
>> own "secure core." It's surely possible and, I honestly believe, a
>> worthy goal. I think for that goal to happen *some day* we need the
>> crypto primitives GnuTLS/libnettle/libhogweed provide, so we don't
>> have to write our own.
DU> Elisp access to crypto primitives doesn't help this either. It must be
DU> entirely written in C then, including IMAP protocol support.
I agree that the solution must be comprehensive and I mentioned ELisp
access could be considered a "tainting" of the secret data. I don't
think ELisp access to the crypto primitives is required, but for ERT
testing for instance it could be allowed with an explicit command-line
option.
DU> By the way, speaking of IMAP, SASL-based authentication is currently
DU> written in Elisp here and there. Perhaps it could be rewritten with
DU> libgsasl? I think this is a concrete use-case, much convincing than
DU> Elisp access to crypto primitives.
I think that would be good and doing it through FFI would be a good use
of that facility, when it's available. I would assume the
lisp/net/sasl.el you wrote is the natural integration point.
Ted
next prev parent reply other threads:[~2014-02-08 16:59 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 [this message]
2014-02-05 8:19 ` Daiki Ueno
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=87wqh5a6b8.fsf@lifelogs.com \
--to=tzz@lifelogs.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.