History log of /netbsd-src/games/factor/Makefile (Results 1 – 15 of 15)
Revision Date Author Comments
# 8499346d 09-May-2023 christos <christos@NetBSD.org>

Handle OpenSSL-3.x


# 84bbce3d 12-Apr-2021 mrg <mrg@NetBSD.org>

include bsd.own.mk to be sure NETBSDSRCDIR is set.


# ef315f79 21-May-2017 riastradh <riastradh@NetBSD.org>

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

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.

show more ...


# ceb0805a 09-Mar-2005 christos <christos@NetBSD.org>

Add -lcrypt where -lcrypto is specified.


# 4eccb08b 08-Feb-2004 jsm <jsm@NetBSD.org>

Separate primes manpage from that of factor. Correct DIAGNOSTICS
information.


# 0be7b964 19-Sep-2002 lukem <lukem@NetBSD.org>

use NETBSDSRCDIR as appropriate


# 69757aee 16-Jun-2002 itojun <itojun@NetBSD.org>

make factor work with and without openssl.


# a311a773 15-Jun-2002 simonb <simonb@NetBSD.org>

Use libcrypto's bignum support to implement a Pollard Rho factoring
algorithm so we can factorise numbers larger than a host long.


# dd1343db 22-Oct-1997 lukem <lukem@NetBSD.org>

use CPPFLAGS instead of CFLAGS


# 10e180cc 08-May-1997 gwr <gwr@NetBSD.org>

Back out the .PATH.c changes. The .depend problem (and others)
will be fixed using the new .NOPATH make feature instead.


# 012e528f 06-May-1997 gwr <gwr@NetBSD.org>

Use .PATH.c: ...


# 42fb1b9d 23-Mar-1995 cgd <cgd@NetBSD.org>

merge with Lite, new RCS id conventions, etc.


# c4c01d75 22-Dec-1994 cgd <cgd@NetBSD.org>

specify man pages the new way.


# cda4f8f6 01-Aug-1993 mycroft <mycroft@NetBSD.org>

Add RCS identifiers.


# 61f28255 21-Mar-1993 cgd <cgd@NetBSD.org>

initial import of 386bsd-0.1 sources