Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/libexec/telnetd/Makefile

33 lines
926 B
Makefile
Raw Normal View History

PR/17999: FUKAUMI Naoki: Support wtmpx entries.
2002-08-20 17:12:00 +04:00
# $NetBSD: Makefile,v 1.33 2002/08/20 13:12:00 christos Exp $
new telnetd from ftp.cray.com. Encryption support ripped out, pending figuring out what to do about it...
1994-02-25 06:20:39 +03:00
# from: @(#)Makefile 8.2 (Berkeley) 12/15/93
Add RCS identifiers.
1993-08-01 09:37:30 +04: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>
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
MAN= telnetd.8
dual-stack telnetd.
1999-07-02 10:32:08 +04:00
CPPFLAGS+=-DINET6
initial import of 386bsd-0.1 sources
1993-03-21 12:45:37 +03:00
PROG= telnetd
Fix for pr 5904 from Zdenek Salvet; we now use openpty() to get a pty.
1998-08-05 04:15:25 +04:00
CPPFLAGS+=-DLINEMODE -DKLUDGELINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOPENPTY_PTY
PR/17999: FUKAUMI Naoki: Support wtmpx entries.
2002-08-20 17:12:00 +04:00
CPPFLAGS+=-DOLD_ENVIRON -DENV_HACK -DSECURELOGIN -DSUPPORT_UTMP -DSUPPORT_UTMPX
new telnetd from ftp.cray.com. Encryption support ripped out, pending figuring out what to do about it...
1994-02-25 06:20:39 +03:00
SRCS= authenc.c global.c slc.c state.c sys_term.c telnetd.c \
initial import of 386bsd-0.1 sources
1993-03-21 12:45:37 +03:00
termstat.c utility.c
- Makefile cleanups
1997-03-25 01:15:37 +03:00
DPADD= ${LIBUTIL} ${LIBTERMCAP} ${LIBTELNET}
update to telnetd from 95.10.23 version. Includes Borman's scrub_env() to keep stuff out of the environment on the way to exec (we already have one in the state machine that keeps them from arriving over the wire, so this should be redundant, but it'll make any further updates easier to have it present). also, RCS Id police.
1996-02-24 04:22:12 +03:00
LDADD+= -lutil -ltermcap -ltelnet
Use ${NETBSDSRCDIR}/some/path instead of ${.CURDIR}/../../some/path
2002-08-19 17:54:34 +04:00
CPPFLAGS+=-I${NETBSDSRCDIR}/lib
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
CPPFLAGS+=-I${.CURDIR}
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
CPPFLAGS+=-I${DESTDIR}/usr/include/krb5
CPPFLAGS+=-DKRB5
Merge a bunch of things from crypto-us and crypto-intl into basesrc, adding support for Heimdal/KTH Kerberos where easy to do so. Eliminate bsd.crypto.mk. There is still a bunch more work to do, but crypto is now more-or-less fully merged into the base NetBSD distribution.
2000-06-20 10:00:24 +04:00
Use ${NETBSDSRCDIR}/some/path instead of ${.CURDIR}/../../some/path
2002-08-19 17:54:34 +04:00
VERS!= cd ${NETBSDSRCDIR}/lib/libvers && ${PRINTOBJDIR}
link against the not-installed libvers
2000-08-04 02:47:37 +04:00
LDADD+= -lkrb5 -lkrb -lcrypto -lasn1 -lcom_err -L${VERS} -lvers -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
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
Use bsd.crypto.mk.
1999-07-13 02:04:09 +04:00
.include <bsd.prog.mk>