Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/usr.bin/telnet/Makefile

67 lines
2.5 KiB
Makefile
Raw Normal View History

Split the notion of building Hesiod, Kerberos, S/key, and YP infrastructure and using that infrastructure in programs. * MKHESIOD, MKKERBEROS, MKSKEY, and MKYP control building of the infratsructure (libraries, support programs, etc.) * USE_HESIOD, USE_KERBEROS, USE_SKEY, and USE_YP control building of support for using the corresponding API in various libraries/programs that can use it. As discussed on tech-toolchain.
2002-03-22 21:10:19 +03:00
# $NetBSD: Makefile,v 1.26 2002/03/22 18:10:24 thorpej Exp $
initial import of 386bsd-0.1 sources
1993-03-21 12:45:37 +03:00
#
# Copyright (c) 1990 The Regents of the University of California.
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
# 3. All advertising materials mentioning features or use of this software
# must display the following acknowledgement:
# This product includes software developed by the University of
# California, Berkeley and its contributors.
# 4. Neither the name of the University nor the names of its contributors
# may be used to endorse or promote products derived from this software
# without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
#
new telnet from ftp.cray.com. Encryption support ripped out, pending figuring out what to do about it...
1994-02-25 06:00:16 +03:00
# from: @(#)Makefile 8.1 (Berkeley) 6/6/93
initial import of 386bsd-0.1 sources
1993-03-21 12:45:37 +03:00
#
Add MK... variables to enable/disable various aspects of building crypto support into the system. See share/mk/bsd.README for more a full description.
2000-06-23 10:01:10 +04:00
.include <bsd.own.mk>
initial import of 386bsd-0.1 sources
1993-03-21 12:45:37 +03:00
PROG= telnet
use CPPFLAGS instead of CFLAGS
1997-10-24 13:00:17 +04:00
CPPFLAGS+=-DTERMCAP -DKLUDGELINEMODE -DUSE_TERMIO -Dunix
CPPFLAGS+=-DENV_HACK
Use bsd.crypto.mk.
1999-07-13 02:11:37 +04:00
CPPFLAGS+=-I${.CURDIR}
IPv6-ready telnet. source route (telnet @localhost@localhost) works for IPv6 as well.
1999-07-02 19:09:10 +04:00
LDADD+= -ltermcap -ltelnet
Use bsd.crypto.mk.
1999-07-13 02:11:37 +04:00
DPADD+= ${LIBTERMCAP} ${LIBTELNET}
initial import of 386bsd-0.1 sources
1993-03-21 12:45:37 +03:00
SRCS= authenc.c commands.c main.c network.c ring.c sys_bsd.c telnet.c \
Bring the telnet situation back into better shape. Specifically, pull in just about all of the differences from the crypto-us telnet suite (which includes Kerberos 4 and connection encryption support). Also bring in the Kerberos 5 support from the Heimdal telnet, and frob a little so that it can work with the non-Heimdal telnet suite. There is still some work left to do, specifically: - Add Heimdal's ticket forwarding support to the Berkeley Kerberos 4 module. - Add connection encryption support to the Heimdal Kerberos 5 module. Hints on this can be taken from the MIT Kerberos 5 module which still exists in crypto-us. However, even with the shortcomings listed above, this is a better situation than using the stock Heimdal telnet suite, which does not understand the IPSec policy stuff, and is also based on much older code which contains bugs that we have already fixed in the NetBSD sources.
2000-06-22 10:47:42 +04:00
terminal.c tn3270.c utilities.c
new telnet from ftp.cray.com. Encryption support ripped out, pending figuring out what to do about it...
1994-02-25 06:00:16 +03:00
Bring the telnet situation back into better shape. Specifically, pull in just about all of the differences from the crypto-us telnet suite (which includes Kerberos 4 and connection encryption support). Also bring in the Kerberos 5 support from the Heimdal telnet, and frob a little so that it can work with the non-Heimdal telnet suite. There is still some work left to do, specifically: - Add Heimdal's ticket forwarding support to the Berkeley Kerberos 4 module. - Add connection encryption support to the Heimdal Kerberos 5 module. Hints on this can be taken from the MIT Kerberos 5 module which still exists in crypto-us. However, even with the shortcomings listed above, this is a better situation than using the stock Heimdal telnet suite, which does not understand the IPSec policy stuff, and is also based on much older code which contains bugs that we have already fixed in the NetBSD sources.
2000-06-22 10:47:42 +04:00
CPPFLAGS+=-I${.CURDIR}/../../lib
Unlike other domestic bits, telnet and telnetd are never built as a part of the domestic build process. No domestic program actually builds its own man pages but instead relies on those built in the exportable tree. The result is missing telnet(1) and telnet(8) pages. Fix this problem descending into the telnet and telnetd directories regardless of whether we're doing an exportable build or not. Once there, we generate only the man pages if we're building a non-exportable system.
1998-07-23 02:30:07 +04:00
IPv6-ready telnet. source route (telnet @localhost@localhost) works for IPv6 as well.
1999-07-02 19:09:10 +04:00
CPPFLAGS+=-DIPSEC
LDADD+= -lipsec
DPADD+= ${LIBIPSEC}
CPPFLAGS+=-DINET6
Split the notion of building Hesiod, Kerberos, S/key, and YP infrastructure and using that infrastructure in programs. * MKHESIOD, MKKERBEROS, MKSKEY, and MKYP control building of the infratsructure (libraries, support programs, etc.) * USE_HESIOD, USE_KERBEROS, USE_SKEY, and USE_YP control building of support for using the corresponding API in various libraries/programs that can use it. As discussed on tech-toolchain.
2002-03-22 21:10:19 +03:00
.if (${USE_KERBEROS} != "no")
Bring the telnet situation back into better shape. Specifically, pull in just about all of the differences from the crypto-us telnet suite (which includes Kerberos 4 and connection encryption support). Also bring in the Kerberos 5 support from the Heimdal telnet, and frob a little so that it can work with the non-Heimdal telnet suite. There is still some work left to do, specifically: - Add Heimdal's ticket forwarding support to the Berkeley Kerberos 4 module. - Add connection encryption support to the Heimdal Kerberos 5 module. Hints on this can be taken from the MIT Kerberos 5 module which still exists in crypto-us. However, even with the shortcomings listed above, this is a better situation than using the stock Heimdal telnet suite, which does not understand the IPSec policy stuff, and is also based on much older code which contains bugs that we have already fixed in the NetBSD sources.
2000-06-22 10:47:42 +04:00
CPPFLAGS+=-DAUTHENTICATION -DENCRYPTION -DKRB4
CPPFLAGS+=-DKRB5 -DFORWARD
link against the not-installed libvers
2000-08-04 02:47:37 +04:00
LDADD+= -lkrb5 -lkrb -lcrypto -lasn1 -lcom_err -lroken
Bring the telnet situation back into better shape. Specifically, pull in just about all of the differences from the crypto-us telnet suite (which includes Kerberos 4 and connection encryption support). Also bring in the Kerberos 5 support from the Heimdal telnet, and frob a little so that it can work with the non-Heimdal telnet suite. There is still some work left to do, specifically: - Add Heimdal's ticket forwarding support to the Berkeley Kerberos 4 module. - Add connection encryption support to the Heimdal Kerberos 5 module. Hints on this can be taken from the MIT Kerberos 5 module which still exists in crypto-us. However, even with the shortcomings listed above, this is a better situation than using the stock Heimdal telnet suite, which does not understand the IPSec policy stuff, and is also based on much older code which contains bugs that we have already fixed in the NetBSD sources.
2000-06-22 10:47:42 +04:00
DPADD+= ${LIBKRB5} ${LIBKRB} ${LIBCRYPTO} ${LIBASN1} ${LIBCOM_ERR} ${LIBROKEN}
Add MK... variables to enable/disable various aspects of building crypto support into the system. See share/mk/bsd.README for more a full description.
2000-06-23 10:01:10 +04:00
.endif
Use bsd.crypto.mk.
1999-07-13 02:11:37 +04:00
.include <bsd.prog.mk>