wireguard-openbsd/regress/usr.bin/ssh/keys-command.sh, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/regress/usr.bin/ssh/keys-command.sh?h=jd%2Fqueueboosts 2019-07-25T08:48:11Z Switch keys-command test from rsa to ed25519 since it's supported for 2019-07-25T08:48:11Z dtucker dtucker@openbsd.org 2019-07-25T08:48:11Z urn:sha1:662f0e3fe28c75e4b9eea128c27d244decba8432 both OpenSSL and non-OpenSSL builds. Append pid to temp files in /var/run and set a cleanup trap for them. 2018-11-22T08:48:32Z dtucker dtucker@openbsd.org 2018-11-22T08:48:32Z urn:sha1:79792e0afb96a5956df25e273b4b09213ab99281 This allows multiple instances of tests to run without colliding. Allow to run ssh regression tests as root. If the user is already 2016-09-26T21:34:38Z bluhm bluhm@openbsd.org 2016-09-26T21:34:38Z urn:sha1:2078aca3aeb91c5f2fb44272c0ccf71714b4a550 root, the test should not expect that SUDO is set. If ssh needs another user, use sudo or doas to switch from root if necessary. OK dtucker@ regress test for AuthorizedKeysCommand arguments 2015-05-21T06:40:02Z djm djm@openbsd.org 2015-05-21T06:40:02Z urn:sha1:37b875d2ad842846dfb277e895434ec8db2c945d Fix some problems with the keys-command test: 2012-12-06T06:06:54Z dtucker dtucker@openbsd.org 2012-12-06T06:06:54Z urn:sha1:a477ac7cb86150591698ac8b7b24593f591b4c73 - use string comparison rather than numeric comparison - check for existing KEY_COMMAND file and don't clobber if it exists - clean up KEY_COMMAND file if we do create it. - check that KEY_COMMAND is executable (which it won't be if eg /var/run is mounted noexec). ok djm. regress for AuthorizedKeysCommand; hints from markus@ 2012-11-22T22:49:30Z djm djm@openbsd.org 2012-11-22T22:49:30Z urn:sha1:a796a46a36bff520286c924c03eb0ca659b27905