From 27377706d3d5cbb243faa015aca47493cbe67b14 Mon Sep 17 00:00:00 2001 From: dtucker Date: Fri, 13 Jan 2023 04:23:00 +0000 Subject: [PATCH] Add scp's path to test sshd's PATH. If the scp we're testing is fully qualified (eg it's not in the system PATH) then add its path to the under-test sshd's PATH so we can find it. Prompted by bz#3518. --- regress/usr.bin/ssh/test-exec.sh | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/regress/usr.bin/ssh/test-exec.sh b/regress/usr.bin/ssh/test-exec.sh index 55874921ea7..8f26b596175 100644 --- a/regress/usr.bin/ssh/test-exec.sh +++ b/regress/usr.bin/ssh/test-exec.sh @@ -1,4 +1,4 @@ -# $OpenBSD: test-exec.sh,v 1.92 2022/07/25 07:12:45 dtucker Exp $ +# $OpenBSD: test-exec.sh,v 1.93 2023/01/13 04:23:00 dtucker Exp $ # Placed in the Public Domain. #SUDO=sudo @@ -332,6 +332,13 @@ cat << EOF > $OBJ/sshd_config Subsystem sftp $SFTPSERVER EOF +# If we're testing a non-installed scp, add its directory to sshd's PATH +# so we can test it. +case "$SCP" in +/*) PATH_WITH_SCP="`dirname $SCP`:$PATH" + echo " SetEnv PATH='$PATH_WITH_SCP'" >>$OBJ/sshd_config ;; +esac + # This may be necessary if /usr/src and/or /usr/obj are group-writable, # but if you aren't careful with permissions then the unit tests could # be abused to locally escalate privileges. -- 2.20.1