Get ready to handle the openssl move from bsd -> apache2

branches: 1.15.16;
Oops forgot one openssl version name change

pretend we have openssl-1.1

switch everyone to openssl.old

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.

libcrypto moved.

Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on the
FORTIFY_SOURCE feature of libssp, thus checking the size of arguments to
various string and memory copy and set functions (as well as a few system
calls and other miscellany) where known at function entry. RedHat has
evidently built all "core system packages" with this option for some time.

This option should be used at the top of Makefiles (or Makefile.inc where
this is used for subdirectories) but after any setting of LIB.

This is only useful for userland code, and cannot be used in libc or in
any code which includes the libc internals, because it overrides certain
libc functions with macros. Some effort has been made to make USE_FORT=yes
work correctly for a full-system build by having the bsd.sys.mk logic
disable the feature where it should not be used (libc, libssp iteself,
the kernel) but no attempt has been made to build the entire system with
USE_FORT and doing so will doubtless expose numerous bugs and misfeatures.

Adjust the system build so that all programs and libraries that are setuid,
directly handle network data (including serial comm data), perform
authentication, or appear likely to have (or have a history of having)
data-driven bugs (e.g. file(1)) are built with USE_FORT=yes by default,
with the exception of libc, which cannot use USE_FORT and thus uses
only USE_SSP by default. Tested on i386 with no ill results; USE_FORT=no
per-directory or in a system build will disable if desired.

use LIBDPLIBS for libcrypto.

Adjust to the new openssl build; bump version. Also if we are compiling
with SSL, link against libcrypto to pick up the proper versions of the
symbols needed.

Put back exit on warning for lint.

This needs work to pass lint - whic I'm not going to invest.
Make lint not treat warnings as errors.

Get rid of liblibradius; hi manu.

Oops, include dir.

Add include files.

Pass lint and WARNS=3

branches: 1.1.1;
Initial revision

branches: 1.1.2;
file Version.map was initially added on branch agc-symver.

u_intN_t -> uintN_t

branches: 1.1.1;
Initial revision

Remove duplicate .Pp. XXX: References non-existing rad_config(3).

branches: 1.1.1;
Initial revision

branches: 1.1.4;
libradius: Add expected symbols list.

PR lib/58838: shared libraries in base should all have expsym lists

Adjust to openssl 1.1

Fix build by making split return a size_t:
src/lib/libradius/radlib.c(1053): warning: conversion from 'unsigned long'
to 'int' may lose accuracy [132]

fix -Wsign-compare issues

no point in using alloca here.

add more casts.

Adjust to the new openssl build; bump version. Also if we are compiling
with SSL, link against libcrypto to pick up the proper versions of the
symbols needed.

Fix compilation both with and without SSL. The buffer argument is different
type, not just the length.

GCC 2.95.3 doesn't like macros to be called with no argument when
the definition has an argument. Cheesily add a 0 argument to the
srandomdev() invocation (which gets defined as null on NetBSD).
Restores our vax port to a buildable state.

Make conversions from unsigned long to int explicit via casts,
rather than imiplicit, which causes lint heart burn ("conversion
from 'unsigned long' to 'int' may lose accuracy).

Fix lint on 64 bit machines.

Pass lint and WARNS=3

branches: 1.1.1;
Initial revision

Pass lint and WARNS=3

branches: 1.1.1;
Initial revision

fix -Wsign-compare issues

change some ints to size_t

Pass lint and WARNS=3

branches: 1.1.1;
Initial revision

Pass lint and WARNS=3

branches: 1.1.1;
Initial revision

Recursively revbump all dependents of libcrypto.

Otherwise any existing software linked against the openssl11
libcrypto.so.14 and any of these libraries will suddenly start
pulling in libcrypto.so.15 at the same time, leading to mayhem in the
address space.

PR lib/57603

XXX pullup-10

branches: 1.5.56;
bump libcrypto and friends; OpenSSL abi change: do_cipher last argument
changed from u_int to size_t. Affects _LP64 only.

bump shared libraries.

Recursively bump the major version number of the shared libraries
which use libcrypto (and those which use those libraries again),
as libcrypto's major number was recently bumped. The pam modules
share a major with libpam, so they are all bumped as well.

branches: 1.2.18; 1.2.20;
Adjust to the new openssl build; bump version. Also if we are compiling
with SSL, link against libcrypto to pick up the proper versions of the
symbols needed.

branches: 1.1.1;
Initial revision