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

42 lines
1.1 KiB
Makefile
Raw Normal View History

Userland now builds and uses terminfo instead of termcap. OK: core@, jdc@
2010-02-03 18:34:37 +03:00
# $NetBSD: Makefile,v 1.46 2010/02/03 15:34:43 roy 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
Default to WARNS=4 Exceptions that need a lower level are: getty ld.elf_so lfs_cleanerd makewhatis telnetd tftpd hpropd ipropd-master ipropd-slave kadmind kpasswdd
2009-03-16 05:24:55 +03:00
WARNS?= 2 # XXX: const issues in sys_term.c
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
initial import of 386bsd-0.1 sources
1993-03-21 12:45:37 +03:00
PROG= telnetd
remove unneeded #ifdefs. improves readability. (confirmed that exact same *.o is produced)
2003-07-14 19:55:53 +04:00
CPPFLAGS+=-DLINEMODE -DKLUDGELINEMODE -DDIAGNOSTICS
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
Userland now builds and uses terminfo instead of termcap. OK: core@, jdc@
2010-02-03 18:34:37 +03:00
DPADD= ${LIBTELNETDIR}/libtelnet.a ${LIBTERMINFO} ${LIBUTIL}
LDADD+= ${LIBTELNETDIR}/libtelnet.a -lterminfo -lutil
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
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}
stop installing install libtelnet. build under lib/libtelnet and reference it from usr.bin/telnet and libexec/telnetd. (reason for separate build: compiler flags)
2003-07-16 09:42:01 +04:00
LIBTELNETDIR!= cd ${.CURDIR}/../../lib/libtelnet; ${PRINTOBJDIR}
Fix the checkflist for builds without Kerberos 4 (MKKERBEROS4=no) and without Kerberos 4 & 5 (MKKERBEROS=no). Previously checkflist complained of missing files. * move kerberos- and kerberos 4-only files into new flists, distrib/sets/lists/*/krb.* * make the flist generators grok MKKERBEROS{,4} variables * fix Makefiles which treat MKKERBEROS=no as MKKERBEROS5=no. 9 out of 10 experts agree that it is ludicrous to build w/ KERBEROS4 and w/o KERBEROS5. * fix header files, also, which treat MKKERBEROS=no as MKKERBEROS5=no. * omit some Kerberos-only subdirectories from the build as MKKERBEROS{,4} indicate (I acknowledge the sentiment that flists are the wrong way to go, and that the makefiles should produce the metalog directly. That sounds to me like the right way to go, but I am not prepared to do revamp all the makefiles. While my approach is expedient, it fits painlessly within the current build architecture until we are delivered from flist purgatory, and it does not postpone our delivery. Fair enough?)
2003-12-11 12:46:26 +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+=-I${DESTDIR}/usr/include/krb5
rearrange lib stuff so that these link on non-shared-lib platforms.
2003-12-14 01:07:35 +03:00
CPPFLAGS+=-DKRB5 -DAUTHENTICATION -DENCRYPTION
Add -lcrypt to link lines for applications using -lkrb5, so that they link successfully when MKPIC=no, as is always the case for our ports which do not support shared libraries. Discussed with thorpej and christos.
2005-03-04 23:44:55 +03:00
LDADD+= -lkrb5 -lasn1 -lcrypto -lcrypt
DPADD+= ${LIBKRB5} ${LIBASN1} ${LIBCRYPTO} ${LIBCRYPT}
split MKKERBEROS4 from MKKERBEROS. based on work by lha at stacken.kth.se (build confirmed with both MKKERBEROS4=yes and MKKERBEROS4=no)
2003-07-23 12:01:24 +04:00
Add pam glue.
2005-02-20 11:52:10 +03:00
.if (${USE_PAM} != "no")
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.
2005-03-04 23:41:08 +03:00
LDADD+= -lpam ${PAM_STATIC_LDADD}
DPADD+= ${LIBPAM} ${PAM_STATIC_DPADD}
Add pam glue.
2005-02-20 11:52:10 +03:00
.endif
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
Move linking with libdes to the common kerberos section since libtelnet depends on the old des functions. From Jukka Salmi in NetBSD pr misc/28727
2004-12-22 04:25:05 +03:00
LDADD+= -ldes -lcom_err -L${VERS} -lvers -lroken
DPADD+= ${LIBDES} ${LIBCOM_ERR} ${LIBROKEN}
split MKKERBEROS4 from MKKERBEROS. based on work by lha at stacken.kth.se (build confirmed with both MKKERBEROS4=yes and MKKERBEROS4=no)
2003-07-23 12:01:24 +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
.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>
Reference in New Issue Copy Permalink