all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: SHA, MD, and openssl
Date: Sun, 08 Dec 2013 17:46:09 -0500	[thread overview]
Message-ID: <877gbfvu4u.fsf@flea.lifelogs.com> (raw)
In-Reply-To: 52A4DE34.7060407@cs.ucla.edu

On Sun, 08 Dec 2013 13:01:40 -0800 Paul Eggert <eggert@cs.ucla.edu> wrote: 

PE> Eli Zaretskii wrote:
>> However, isn't it true that openssl has some legal "issues" with
>> patents and with its license, and shouldn't we prefer libnettle for
>> those reasons?

PE> I'm not aware of any patent issues for SHA or MD5.
PE> As for as license, Emacs is linking against a library
PE> that is normally distributed with the major components of
PE> the operating system, so that part of the GPL applies.

PE> It'd make sense for Emacs to use gnutls, nettle, libgcrypt,
PE> etc. if available and if the performance is good.
PE> This has been suggested on the gnulib list and patches
PE> along those lines would be gratefully accepted.
PE> See, for example:

PE> http://lists.gnu.org/archive/html/bug-gnulib/2013-12/msg00024.html
PE> http://lists.gnu.org/archive/html/bug-gnulib/2013-12/msg00026.html
PE> http://lists.gnu.org/archive/html/bug-gnulib/2013-12/msg00036.html

I wrote the full integration with libnettle+libhogweed as a patch (with
tests, and bringing in all the interesting ciphers).  It later turned
out that GnuTLS, already a requirement, exposes all that at the C level
in passthrough functions, so libnettle and libhogweed are not even a
requirement.  But that's an implementation detail, since GnuTLS requires
libnettle and libhogweed anyway.

Stefan rejected the patch because he wants to move the GnuTLS
integration to a FFI layer[1].  I don't know when I'll have time to
implement that myself so any help is welcome.

Ted

[1] https://lists.gnu.org/archive/html/emacs-devel/2013-10/msg00168.html




  parent reply	other threads:[~2013-12-08 22:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-08 19:33 SHA, MD, and openssl Eli Zaretskii
2013-12-08 21:01 ` Paul Eggert
2013-12-08 21:11   ` Eli Zaretskii
2013-12-08 22:44     ` Paul Eggert
2013-12-08 22:46   ` Ted Zlatanov [this message]
2013-12-09 13:07     ` Ted Zlatanov
2013-12-10  2:31       ` Stefan Monnier
2013-12-09 18:08   ` Richard Stallman
2013-12-10  1:51     ` Stephen J. Turnbull
2013-12-10 14:31       ` Richard Stallman
2013-12-10 18:52         ` Paul Eggert
2013-12-11 15:13           ` Richard Stallman
2013-12-11 18:54             ` Paul Eggert
2013-12-11 20:15               ` Pádraig Brady
2013-12-12  3:11                 ` Glenn Morris
2013-12-12  6:08                 ` Stephen J. Turnbull
2013-12-12 10:15               ` Richard Stallman
2013-12-12 12:45                 ` Pádraig Brady
2013-12-13 12:21                   ` Richard Stallman
2013-12-13 13:58                     ` Pádraig Brady
2013-12-14  1:01                       ` Richard Stallman
2013-12-09 22:02   ` Rüdiger Sonderfeld

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=877gbfvu4u.fsf@flea.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.