src/secure/Makefile, branch stable/8

MFC r201210:

2010-04-06T10:32:26+00:00

Remove pppd, it's gone.

Reimplementation of world/kernel build options. For details, see:

2006-03-17T18:54:44+00:00

http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html

The src.conf(5) manpage is to follow in a few days.

Brought to you by:	imp, jhb, kris, phk, ru (all bugs are mine)

NOCRYPT -> NO_CRYPT

2004-12-21T10:16:04+00:00

Fix release builds (release.3 target). We also need to rebuild libradius,

2004-05-02T17:38:27+00:00

because otherwise it will remain having a dependency upon libssl. This
breaks the non-crypto build that happens for release.3

While here, order the list of programs and libraries.

Speculating review feedback from: ru

Added two utility targets "secure" and "insecure", analogous to

2004-01-18T07:44:53+00:00

"kerberize" and "dekerberize" in kerberos5/Makefile.  These can
be used to recompile bits with optional crypto support with and
without crypto, respectively.

Reviewed by:	markm

Once upon a time we had both "crypto" and "krb5" distributions,

2004-01-17T19:22:36+00:00

and rebuilt some bits with crypto but without Kerberos support
(most notably SSH) during "make release", to put them into the
"crypto" distribution.

Now that we don't ship the separate "krb5" distribution anymore
(it's now part of the "crypto" distribuion), don't waste time
recompiling SSH bits without crypto and without Kerberos support
in an attempt to put them in the "base" distribution -- it just
doesn't work as SSH always uses crypto code.

We avoid this by not rebuilding KPROGS from kerberos5/Makefile in
release/Makefile and adding "libpam" to SPROGS in secure/Makefile
to ensure it's still rebuilt without crypto support for the "base"
distribution.  (Disabling crypto (NOCRYPT) also disables building
of Kerberos-related PAM modules, and it's OK to depend on this.)

This should be a no-op change saving some "make release" time.

- Properly build both crypto and non-crypto versions of the

2004-01-17T13:41:16+00:00

  package management tools.

- Drop redundant dependency of pkg_create(1) and pkg_delete(1)
  on crypto libraries now that they do not link with libfetch.

Removed well outdated comment.

2004-01-17T03:12:46+00:00

Very big makeover in the way telnet, telnetd and libtelnet are built.

2003-07-16T20:59:15+00:00

Previously, there were two copies of telnet; a non-crypto version
that lived in the usual places, and a crypto version that lived in
crypto/telnet/. The latter was built in a broken manner somewhat akin
to other "contribified" sources. This meant that there were 4 telnets
competing with each other at build time - KerberosIV, Kerberos5,
plain-old-secure and base. KerberosIV is no longer in the running, but
the other three took it in turns to jump all over each other during a
"make buildworld".

As the crypto issue has been clarified, and crypto _calls_ are not
a problem, crypto/telnet has been repo-copied to contrib/telnet,
and with this commit, all telnets are now "contribified". The contrib
path was chosen to not destroy history in the repository, and differs
from other contrib/ entries in that it may be worked on as "normal"
BSD code. There is no dangerous crypto in these sources, only a
very weak system less strong than enigma(1).

Kerberos5 telnet and Secure telnet are now selected by using the usual
macros in /etc/make.conf, and the build process is unsurprising and
less treacherous.

Drop this MAINTAINER bit. I'll reclaim an "Advisory Maintainership"

2003-06-04T16:10:20+00:00

for this area later.