bsd.own.mk: rename GCC_NO_* to CC_WNO_*

Rename compiler-warning-disable variables from
GCC_NO_warning
to
CC_WNO_warning
where warning is the full warning name as used by the compiler.

GCC_NO_IMPLICIT_FALLTHRU is CC_WNO_IMPLICIT_FALLTHROUGH

Using the convention CC_compilerflag, where compilerflag
is based on the full compiler flag name.

accommodate OpenSSL-3.x

Fix broken build with MKKERBEROS=no

Conditionalize GSSAPI use on USE_KERBEROS

Merge openldap-2.5.6.

use GCC_NO_STRINGOP_OVERFLOW for charray.c.

this only affects some platforms.

branches: 1.9.4;
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.

Update for building OpenLDAP 2.4.39.

branches: 1.6.12; 1.6.24;
update for .c changes in 2.4.21

depend on the proper libcrypto

reference other libraries from their relative location.

branches: 1.3.2;
support MKCRYPTO==no. approved by lukem.

Add assertion.c to SRCS (introduced in 2.4.9->2.4.11 merge)

branches: 1.1.2; 1.1.4;
NetBSD reachover build framework for OpenLDAP.
Inspired by framework kindly donated by Wasabi Systems.

Fix broken build with MKKERBEROS=no

Conditionalize GSSAPI use on USE_KERBEROS

Merge openldap-2.5.6.

use GCC_NO_STRINGOP_OVERFLOW for charray.c.

this only affects some platforms.

branches: 1.9.4;
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.

Update for building OpenLDAP 2.4.39.

branches: 1.6.12; 1.6.24;
update for .c changes in 2.4.21

depend on the proper libcrypto

reference other libraries from their relative location.

branches: 1.3.2;
support MKCRYPTO==no. approved by lukem.

Add assertion.c to SRCS (introduced in 2.4.9->2.4.11 merge)

branches: 1.1.2; 1.1.4;
NetBSD reachover build framework for OpenLDAP.
Inspired by framework kindly donated by Wasabi Systems.

Conditionalize GSSAPI use on USE_KERBEROS

Merge openldap-2.5.6.

use GCC_NO_STRINGOP_OVERFLOW for charray.c.

this only affects some platforms.

branches: 1.9.4;
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.

Update for building OpenLDAP 2.4.39.

branches: 1.6.12; 1.6.24;
update for .c changes in 2.4.21

depend on the proper libcrypto

reference other libraries from their relative location.

branches: 1.3.2;
support MKCRYPTO==no. approved by lukem.

Add assertion.c to SRCS (introduced in 2.4.9->2.4.11 merge)

branches: 1.1.2; 1.1.4;
NetBSD reachover build framework for OpenLDAP.
Inspired by framework kindly donated by Wasabi Systems.

use GCC_NO_STRINGOP_OVERFLOW for charray.c.

this only affects some platforms.

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.

Update for building OpenLDAP 2.4.39.

branches: 1.6.12; 1.6.24;
update for .c changes in 2.4.21

depend on the proper libcrypto

reference other libraries from their relative location.

branches: 1.3.2;
support MKCRYPTO==no. approved by lukem.

Add assertion.c to SRCS (introduced in 2.4.9->2.4.11 merge)

branches: 1.1.2; 1.1.4;
NetBSD reachover build framework for OpenLDAP.
Inspired by framework kindly donated by Wasabi Systems.

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.

Update for building OpenLDAP 2.4.39.

branches: 1.6.12; 1.6.24;
update for .c changes in 2.4.21

depend on the proper libcrypto

reference other libraries from their relative location.

branches: 1.3.2;
support MKCRYPTO==no. approved by lukem.

Add assertion.c to SRCS (introduced in 2.4.9->2.4.11 merge)

branches: 1.1.2; 1.1.4;
NetBSD reachover build framework for OpenLDAP.
Inspired by framework kindly donated by Wasabi Systems.