summaryrefslogtreecommitdiffstats
path: root/factor
diff options
context:
space:
mode:
authorriastradh <riastradh@NetBSD.org>2017-05-21 15:28:36 +0000
committerriastradh <riastradh@NetBSD.org>2017-05-21 15:28:36 +0000
commitebf5607d13ea61beb26b2e17e57679c826c26933 (patch)
tree748d0afa6e7451a00cc1e62f8b5232bab2349a72 /factor
parent45f14ee49bbb0208d52001a456721bb00c43f429 (diff)
downloadbsdgames-darwin-ebf5607d13ea61beb26b2e17e57679c826c26933.tar.gz
bsdgames-darwin-ebf5607d13ea61beb26b2e17e57679c826c26933.tar.zst
bsdgames-darwin-ebf5607d13ea61beb26b2e17e57679c826c26933.zip
Remove MKCRYPTO option.
Originally, MKCRYPTO was introduced because the United States classified cryptography as a munition and restricted its export. The export controls were substantially relaxed fifteen years ago, and are essentially irrelevant for software with published source code. In the intervening time, nobody bothered to remove the option after its motivation -- the US export restriction -- was eliminated. I'm not aware of any other operating system that has a similar option; I expect it is mainly out of apathy for churn that we still have it. Today, cryptography is an essential part of modern computing -- you can't use the internet responsibly without cryptography. The position of the TNF board of directors is that TNF makes no representation that MKCRYPTO=no satisfies any country's cryptography regulations. My personal position is that the availability of cryptography is a basic human right; that any local laws restricting it to a privileged few are fundamentally immoral; and that it is wrong for developers to spend effort crippling cryptography to work around such laws. As proposed on tech-crypto, tech-security, and tech-userlevel to no objections: https://mail-index.netbsd.org/tech-crypto/2017/05/06/msg000719.html https://mail-index.netbsd.org/tech-security/2017/05/06/msg000928.html https://mail-index.netbsd.org/tech-userlevel/2017/05/06/msg010547.html P.S. Reviewing all the uses of MKCRYPTO in src revealed a lot of *bad* crypto that was conditional on it, e.g. DES in telnet... That should probably be removed too, but on the grounds that it is bad, not on the grounds that it is (nominally) crypto.
Diffstat (limited to 'factor')
-rw-r--r--factor/Makefile7
1 files changed, 1 insertions, 6 deletions
diff --git a/factor/Makefile b/factor/Makefile
index 8fee6f06..8f69170e 100644
--- a/factor/Makefile
+++ b/factor/Makefile
@@ -1,20 +1,15 @@
-# $NetBSD: Makefile,v 1.12 2005/03/09 03:11:21 christos Exp $
+# $NetBSD: Makefile,v 1.13 2017/05/21 15:28:41 riastradh Exp $
# @(#)Makefile 8.1 (Berkeley) 5/31/93
-# For MKCRYPTO
-.include <bsd.own.mk>
-
PRIMES= ${NETBSDSRCDIR}/games/primes
PROG= factor
SRCS= factor.c pr_tbl.c
CPPFLAGS+=-I${PRIMES}
-.if (${MKCRYPTO} != "no")
CPPFLAGS+=-DHAVE_OPENSSL
LDADD+= -lcrypto -lcrypt
DPADD+= ${LIBCRYPTO} ${LIBCRYPT}
-.endif
MAN= factor.6
.PATH: ${PRIMES}