From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: SHA, MD, and openssl
Date: Sun, 08 Dec 2013 14:44:40 -0800 [thread overview]
Message-ID: <52A4F658.50301@cs.ucla.edu> (raw)
In-Reply-To: <83iouzyrnc.fsf@gnu.org>
Eli Zaretskii wrote:
> I meant openssl as a whole.
Emacs trunk won't let Emacs users use openssl as a whole,
only the SHA and MD5 part of libcrypto, so any patent
concerns with other parts of openssl should not be an
issue.
> What about systems where openssl is not normally present out of the
> box? Aren't we encouraging people to install it?
Not particularly. The build will work just fine without openssl,
and no part of the documentation or installation instructions
encourages people to install openssl.
If this turns into a real problem, we can change the installation
instructions to mention that the libcrypto part is intended to be
used only on platforms where libcrypto is normally distributed
with the major components of the operating system.
next prev parent reply other threads:[~2013-12-08 22:44 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 [this message]
2013-12-08 22:46 ` Ted Zlatanov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A4F658.50301@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).