7cca93e61a
Per Austin group issue #884, always set IFS to $' \t\n'. As before, IFS will be exported iff it was in the environment. Most shells (e.g. bash, ksh93 and mksh) already did this. This change improves predictability, in that scripts can simply rely on the default value. However, the effect on security is little, since applications should not be calling the shell with attacker-controlled environment variable names in the first place and other security-sensitive variables such as PATH should be and are imported by the shell. When using a new sh with an old (before 10.2) libc wordexp(), IFS is no longer passed on. Otherwise, wordexp() continues to pass along IFS from the environment per its documentation. Discussed with: pfg Relnotes: yes
30 lines
676 B
Makefile
30 lines
676 B
Makefile
# $FreeBSD$
|
|
|
|
PACKAGE= tests
|
|
|
|
TESTSDIR= ${TESTSBASE}/bin/sh/${.CURDIR:T}
|
|
|
|
.PATH: ${.CURDIR:H}
|
|
ATF_TESTS_SH= functional_test
|
|
|
|
${PACKAGE}FILES+= env1.0
|
|
${PACKAGE}FILES+= exitstatus1.0
|
|
${PACKAGE}FILES+= ifs1.0
|
|
${PACKAGE}FILES+= mail1.0
|
|
${PACKAGE}FILES+= mail2.0
|
|
${PACKAGE}FILES+= optind1.0
|
|
${PACKAGE}FILES+= optind2.0
|
|
${PACKAGE}FILES+= positional1.0
|
|
${PACKAGE}FILES+= positional2.0
|
|
${PACKAGE}FILES+= positional3.0
|
|
${PACKAGE}FILES+= positional4.0
|
|
${PACKAGE}FILES+= positional5.0
|
|
${PACKAGE}FILES+= positional6.0
|
|
${PACKAGE}FILES+= positional7.0
|
|
${PACKAGE}FILES+= positional8.0
|
|
${PACKAGE}FILES+= positional9.0
|
|
${PACKAGE}FILES+= pwd1.0
|
|
${PACKAGE}FILES+= pwd2.0
|
|
|
|
.include <bsd.test.mk>
|