5608fd23c2
1. 50+% of NO_PIE use is fixed by adding -fPIC to INTERNALLIB and other build-only utility libraries. 2. Another 40% is fixed by generating _pic.a variants of various libraries. 3. Some of the NO_PIE use is a bit absurd as it is disabling PIE (and ASLR) where it never would work anyhow, such as csu or loader. This suggests there may be better ways of adding support to the tree. Many of these cases can be fixed such that -fPIE will work but there is really no reason to have it in those cases. 4. Some of the uses are working around hacks done to some Makefiles that are really building libraries but have been using bsd.prog.mk because the code is cleaner. Had they been using bsd.lib.mk then NO_PIE would not have been needed. We likely do want to enable PIE by default (opt-out) for non-tree consumers (such as ports). For in-tree though we probably want to only enable PIE (opt-in) for common attack targets such as remote service daemons and setuid utilities. This is also a great performance compromise since ASLR is expected to reduce performance. As such it does not make sense to enable it in all utilities such as ls(1) that have little benefit to having it enabled. Reported by: kib
16 lines
301 B
Makefile
16 lines
301 B
Makefile
# $FreeBSD$
|
|
|
|
.PATH: ${.CURDIR}/../../contrib/com_err
|
|
|
|
LIBVERS= ${.OBJDIR}/../../kerberos5/lib/libvers/libvers.a
|
|
|
|
PROG= compile_et
|
|
SRCS= compile_et.c parse.y lex.l
|
|
LDADD= -lroken ${LIBVERS}
|
|
DPADD= ${LIBROKEN} ${LIBVERS}
|
|
CFLAGS+=-I. -I${.CURDIR}/../../contrib/com_err
|
|
|
|
WARNS?= 0
|
|
|
|
.include <bsd.prog.mk>
|