Don't try to use sudo inside sshd log wrapper. We still need to
authordtucker <dtucker@openbsd.org>
Tue, 31 Oct 2023 04:15:40 +0000 (04:15 +0000)
committerdtucker <dtucker@openbsd.org>
Tue, 31 Oct 2023 04:15:40 +0000 (04:15 +0000)
commit015a2f38ac009d4ed48a14f2153eafcaf4844e24
treed0659c5bea71736135cae025c270063a0f94eb62
parent84ac6f974db4602fb1fb77802329046dedfb3aac
Don't try to use sudo inside sshd log wrapper.  We still need to
check if we're using sudo since we don't want to chown unecessarily,
as on some platforms this causes an error which pollutes stderr.
We also don't want to unnecessarily invoke sudo, since it's running
in the context of the proxycommand, on *other* platforms it may not
be able to authenticate, and if we're using SUDO then it should
already be privileged.
regress/usr.bin/ssh/test-exec.sh