Move stuff to the common Makefile.racoon
Enable WARNS

Factor out common lex/yacc and warnings handling code.

clean the lex header file.

generate a header file for lex and remove lint prototype warning

racoon: suppress lint warning about C23 compatibility

The code needs to be fixed by upstream.

branches: 1.43.2;
bsd.own.mk: rename to CC_WNO_ADDRESS_OF_PACKED_MEMBER

Provide a single variable
CC_WNO_ADDRESS_OF_PACKED_MEMBER
with options for both clang and gcc, to replace
CLANG_NO_ADDR_OF_PACKED_MEMBER
CC_NO_ADDR_OF_PACKED_MEMBER
GCC_NO_ADDR_OF_PACKED_MEMBER

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

Handle OpenSSL-3.x

deal with OpenSSL-3.x

branches: 1.40.2;
One more ldap change

apply -fcommon to sources that still rely upon it.

Explicitly link liblber and libssl when ldap support is enabled.
Fix sun2, i.e., MKPIC=no build.

Enable ldap support in racoon(8). Proposed on tech-userlevel,
"Go for it" from christos@

add support for new GCC 9 warnings that may be too much to fix
right now. new address-of-packed-member and format-overflow
warnings have new GCC_NO_ADDR_OF_PACKED_MEMBER amd
GCC_NO_FORMAT_OVERFLOW variables to remove these warnings.

apply to a bunch of the tree. mostly, these are real bugs that
should be fixed, but in many cases, only by removing the 'packed'
attribute from some structure that doesn't really need it. (i
looked at many different ones, and while perhaps 60-80% were
already properly aligned, it wasn't clear to me that the uses
were always coming from sane data vs network alignment, so it
doesn't seem safe to remove packed without careful research for
each affect struct.) clang already warned (and was not erroring)
for many of these cases, but gcc picked up dozens more.

add commented out debugging options.

branches: 1.34.2;
add LIBKRB5_LDADD/LIBKRB5_DPADD and their static counterparts
to bsd.prog.mk. use them instead of hard coding various lists
of libraries for krb5.

this fixes static builds.

No RC5 for OpenSSL-1.1

disable compat api setting for openssl 1.1

needs the OpenSSL-1.1 api to build

Remove MKCRYPTO_RC5. Unconditionally include RC5 in libcrypto.so.

This option existed only because RC5 is covered by patents that, twenty
years ago, we had reason to suspect the patent holder, RSA, Inc., might
litigate. The two US patents in question are 5,724,428 and 5,835,600.

According to the USPTO Patent Term Calculator web site at
<https://www.uspto.gov/patent/laws-and-regulations/patent-term-calculator#heading-5>
(retrieved 2017-05-21), patents filed after 1995-06-07 expire twenty
years after the filing date.

number filing date
5,724,428 1995-11-01
5,835,600 1997-04-21

Thus, these patents appear to be expired.

As proposed on tech-crypto and tech-security:

https://mail-index.netbsd.org/tech-crypto/2017/05/05/msg000718.html
https://mail-index.netbsd.org/tech-security/2017/05/05/msg000927.html

GC some GCC 4.8 specific sh3 HACKS entries.

These existed to avoid compile errors, and haven't been effect
since gcc.old was removed.

add sqlite3

branches: 1.27.4; 1.27.6; 1.27.8; 1.27.12; 1.27.14;
more sh3 hacks.

Enable wildcard matching in psk files. We are big kids and if we put a *
in the psk file, we mean it.

branches: 1.25.2;
MKCRYPTO_IDEA is no more

branches: 1.24.2; 1.24.4;
-consistently use "char *" for the compiled policy buffer in the
ipsec_*_policy() functions, as it was documented and used by clients
-remove "ipsec_policy_t" which was undocumented and only present
in the KAME version of the ipsec.h header
-misc cleanup of historical artefacts, and to remove unnecessary
differences between KAME ans FAST_IPSEC

branches: 1.23.4;
Ignore warnings when building with clang for now.

Enable WARNS=4 by default, except for:
cpuctl dumplfs hprop ipf iprop-log kadmin kcm kdc kdigest
kimpersonate kstash ktutil makefs ndbootd ntp pppd quot
racoon racoonctl rtadvd sntp sup tcpdchk tcpdmatch tcpdump
traceroute traceroute6 user veriexecgen wsmoused zic
(Mostly third-party applications)

branches: 1.21.10;
Add more libraries required by libkrb5 etc. in NOPIC case.

Not the right way to fix this.

Because privsep.c uses CMSG_SPACE() to size two local arrays, these
ends up as c99 variable-sized local arrays (CMSG_SPACE() uses a function
as part of calculating its result). This causes the stack protection
code in the compiler to complain, so build this one with -fno-stack-protector
to avoid the problem.

Gets us back to buildability for this program for a number of our ports.

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.

PR/36069: Huang Yushuo: racoon can't work with pam_group
We need -lutil for login_getpwclass

Add the dependendy on libutil

Fix build

Fix ipsec-tools build after recent import

adjust to the new openssl

Add -lcrypt where -lcrypto is specified.

Introduce PAM_STATIC_LDADD and PAM_STATIC_DPADD. When compiling
with MKPIC=no, possibly because the target does not support shared
libraries, these include libraries required to resolve all symbols
which end up referenced from PAM-using applications. The libraries
presently required are -lcrypt, -lrpcsvc and -lutil.

Add use of these variables which are currently set up to use PAM,
so that they compile when MKPIC=no.

Also, in the telnetd case, reorder the order of the libraries, so
that libtelnet.a comes before -ltermcap and -lutil, again to fix
link error when MKPIC=no.

Discussed with thorpej and christos.

Move -lcrypto to the end of the library list, so that this links
without undefined entry points for non-shlib platforms such as sun2.

Define SADB_X_EALG_AESCBC=SADB_X_EALG_AES, as we define SADB_X_EALG_AES
in <net/pfkeyv2.h> while ipsec-tools uses SADB_X_EALG_AESCBC in the code.

Install racoon administrative socket in /var/run instead of /var/racoon

Don't make racoonctl.8 here, it's already done in src/usr.sbin/racoonctl

Add missing racoonctl(8), build with libradius

Additional cleanup pass.

Switch to ipsec-tools for libipsec, setkey, and racoon. From
Emmanuel Dreyfus, with some small changes by me.

Wait for libpfkey to build before descending into racoon, as the
latter depends on the existence of the result of the former.
Fixes parallel build problem.

branches: 1.2.4;
install sample configuration files into /usr/share/examples/racoon.
make variable "SBIN_RACOON" will build static racoon binary, and installs
it into /sbin (nonstandard)

move racoon build framework from sbin/racoon to usr.sbin/racoon.