From: Richard Stallman <rms@gnu.org>
To: Pádraig Brady <P@draigBrady.com>
Cc: eggert@cs.ucla.edu, bug-gnulib@gnu.org, emacs-devel@gnu.org
Subject: Re: SHA, MD, and openssl
Date: Fri, 13 Dec 2013 07:21:55 -0500 [thread overview]
Message-ID: <E1VrRkh-0006hr-MR@fencepost.gnu.org> (raw)
In-Reply-To: <52A9AFDB.1090302@draigBrady.com> (message from Pádraig Brady on Thu, 12 Dec 2013 12:45:15 +0000)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
But SHA1 and SHA256 are commonly available accelerated in hardware.
For this very small subset of routines should we not consider
libcrypto as a system library to these hardware specific interfaces.
This has nothing to do with what we "should consider".
It is a legal criterion stated in the GPL.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call.
next prev parent reply other threads:[~2013-12-13 12:21 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
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 [this message]
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=E1VrRkh-0006hr-MR@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=P@draigBrady.com \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--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.