src/secure/libexec, branch release/5.4.0FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=release%2F5.4.02004-02-05T22:44:25ZFixed style of DPADD and LDADD assignments as per style.Makefile(5).2004-02-05T22:44:25ZRuslan Ermilovru@FreeBSD.org2004-02-05T22:44:25Zurn:sha1:47d7e8a96f52d91b1f0fe5184f0f5d88c897db38Update Makefiles for OpenSSH 3.7.1p2.2004-01-07T11:17:23ZDag-Erling Smørgravdes@FreeBSD.org2004-01-07T11:17:23Zurn:sha1:a04e3d6c3084de022d6bb2144c7a89fd5d8b9f75Explicitly add libz and libcrypto to LDADD for any ssh utilities missing2003-08-19T07:45:03ZGordon Tetlowgordon@FreeBSD.org2003-08-19T07:45:03Zurn:sha1:c45db693122433da0df840aecca85198f1eafb54
it. While not strictly required, it unbreaks the cross-build world that
is resulting from moving the libraries around.
I have a more permanent solution to this problem in the works, but I
asked des for permission to commit this to get the ball rolling. This
also makes the ssh build more along the lines of what the openssh-portable
and OpenBSD openssh Makefile glue does.
Reviewed by: des
Very big makeover in the way telnet, telnetd and libtelnet are built.2003-07-16T20:59:15ZMark Murraymarkm@FreeBSD.org2003-07-16T20:59:15Zurn:sha1:4afa3718327563c785b2961410b6ea85d6ddf3ca
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.
Turn MAKE_KERBEROS5 into NO_KERBEROS by negating the logic. Some extra2003-05-05T07:58:44ZMark Murraymarkm@FreeBSD.org2003-05-05T07:58:44Zurn:sha1:dbf104e68ddd9f971ebc05a68df1e525c3888997
cleanups were necessary in release/Makefile, and the tinderbox code
was syntax checked, not run checked.
The including makefile's directory is tried first for .include "...".2003-04-30T07:54:39ZRuslan Ermilovru@FreeBSD.org2003-04-30T07:54:39Zurn:sha1:f7fa0cbd70e02ecb0c1775218703454d7207deddMost things depend on !defined(NO_OPENSSL); make it look so.2003-04-30T07:51:51ZRuslan Ermilovru@FreeBSD.org2003-04-30T07:51:51Zurn:sha1:6402d39a2b8ca834010410a4de65148adf1a93a6NOSECURE is implied by NOCRYPT, meaning if the latter is defined2003-04-30T07:34:14ZRuslan Ermilovru@FreeBSD.org2003-04-30T07:34:14Zurn:sha1:bce0c9275c90f81acd79138fe4df4b842f254080
we won't be here.
Remove Kerberos IV shims.2003-04-23T17:26:01ZDag-Erling Smørgravdes@FreeBSD.org2003-04-23T17:26:01Zurn:sha1:581ff5e32659ed7d2810fdfedb546fd47c14d9dcUpdate for 3.6.1p1; also remove Kerberos IV shims.2003-04-23T17:25:47ZDag-Erling Smørgravdes@FreeBSD.org2003-04-23T17:25:47Zurn:sha1:d8b043c8d497cc88b50b7cf13479f4766fde5b7f