mirror of https://github.com/wolfSSL/wolfssh.git
f52c3f7e22
Eight scripts saved their starting directory in PWD, which the shell rewrites on every cd, so the "cd $PWD" restore landed in the repository root. sshd_forcedcmd_test.sh's second scenario and the log count in sshd_x509_upn_fail.sh silently never did what they cover. - Save the starting directory in TESTDIR, as sshd_pubkey_reject_test.sh does. - Quote "$TESTDIR" at every cd, now that the saved value is really used. - Stop the daemon from a trap in sshd_forcedcmd_test.sh, so its now reachable second scenario cannot leave one on the shared port when set -e aborts. - Take start_wolfsshd's before and after daemon PID snapshots from pgrep -x instead of scraping every digit run out of "ps -e", which mixed the TIME field's clock digits in with the PID and, with a leftover daemon running, stopped the wrong process. - Let both snapshot pipelines fail, so a set -e caller survives no daemon being up and a daemon that dies after sudo returns is reported by the caller's own empty-PID check. |
||
|---|---|---|
| .. | ||
| wolfssh | ||
| wolfsshd | ||
| include.am | ||
| wolfssh-options.c | ||