bbea88d05d
dangerous! Signal handlers themself must be fixed to not call malloc,
but no pended handlers, it will be correct fix. In finite case each signal
handler can set some variable which will be analized later, but calling
handler functions manually is too dangerous (f.e. signals not blocked while
the handler or handlers switch executed in this case). Of course this
code can be fixed instead of removing, but it not worth fixing in any case.
Should go into 2.2
In addition sig.c code shows following dangerous fragments (there can be more,
but I stop after two):
This fragment
if (fn == SIG_DFL || fn == SIG_IGN) {
handler[sig-1] = (sig_type)0;
<------------- here
signal(sig,fn);
} else {
cause NULL pointer reference when signal comes
"here", but more worse fragment is below:
void handle_signals() {
int sig;
if (caused)
for (sig=0; sig<__MAXSIG; sig++, caused>>=1)
if (caused&1)
(*handler[sig])(sig+1);
}
caused is bitmask which set corresponding bit on each signal coming.
And now imagine, what happens when some signal comes (bit sets) while loop
is executed (see caused>>=1 !!!)
In this light carrier drop situation was (as gdb shows)
1. SIGSEGV in handle_signals because some junk called as *handler reference.
2. Since SIGSEGV was pended too (== never happens),
it can cause various range of disasters.
20 lines
613 B
Makefile
20 lines
613 B
Makefile
# $Id: Makefile,v 1.14 1997/02/22 16:09:55 peter Exp $
|
|
|
|
PROG= ppp
|
|
SRCS= async.c auth.c ccp.c chap.c chat.c command.c filter.c fsm.c hdlc.c \
|
|
ip.c ipcp.c lcp.c lqr.c log.c main.c mbuf.c modem.c os.c \
|
|
pap.c pred.c route.c slcompress.c timer.c systems.c uucplock.c vars.c \
|
|
vjcomp.c arp.c alias.c alias_db.c alias_ftp.c alias_util.c \
|
|
passwdauth.c
|
|
#CFLAGS+= -DHAVE_SHELL_CMD_WITH_ANY_MODE
|
|
CFLAGS += -Wall -DUSE_PERROR -DMSEXT -DPASSWDAUTH
|
|
LDADD += -lmd -lcrypt -lutil
|
|
DPADD += ${LIBMD} ${LIBCRYPT} ${LIBUTIL}
|
|
MAN8= ppp.8
|
|
BINMODE=4555
|
|
BINOWN= root
|
|
|
|
.PATH: ${.CURDIR}/../../sbin/startslip
|
|
|
|
.include <bsd.prog.mk>
|