Save error code from SSH for use inside case statement, from portable.
In some shells, "case" will reset the value of $?, so save it first.

add a comment that could have saved me 45 minutes of wild goose chasing

rename recently-added "valid-before" key restriction to "expiry-time"
as the former is confusing wrt similar terminology in X.509;
pointed out by jsing@

check valid-before option in authorized_keys

for the pty control tests, just check that the PTY path points to
something in /dev (rather than checking the device node itself); makes
life easier for portable, where systems with dynamic ptys can delete
nodes before we get around to testing their existence.

fix testing of pty option, include positive test and testing of
restrict keyword

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

shell portability: use "=" instead of "==" in test(1) expressions,
double-quote string with backslash escaped /

Add regress test for key options. ok djm@

add a comment that could have saved me 45 minutes of wild goose chasing

rename recently-added "valid-before" key restriction to "expiry-time"
as the former is confusing wrt similar terminology in X.509;
pointed out by jsing@

check valid-before option in authorized_keys

for the pty control tests, just check that the PTY path points to
something in /dev (rather than checking the device node itself); makes
life easier for portable, where systems with dynamic ptys can delete
nodes before we get around to testing their existence.

fix testing of pty option, include positive test and testing of
restrict keyword

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

shell portability: use "=" instead of "==" in test(1) expressions,
double-quote string with backslash escaped /

Add regress test for key options. ok djm@

rename recently-added "valid-before" key restriction to "expiry-time"
as the former is confusing wrt similar terminology in X.509;
pointed out by jsing@

check valid-before option in authorized_keys

for the pty control tests, just check that the PTY path points to
something in /dev (rather than checking the device node itself); makes
life easier for portable, where systems with dynamic ptys can delete
nodes before we get around to testing their existence.

fix testing of pty option, include positive test and testing of
restrict keyword

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

shell portability: use "=" instead of "==" in test(1) expressions,
double-quote string with backslash escaped /

Add regress test for key options. ok djm@

for the pty control tests, just check that the PTY path points to
something in /dev (rather than checking the device node itself); makes
life easier for portable, where systems with dynamic ptys can delete
nodes before we get around to testing their existence.

fix testing of pty option, include positive test and testing of
restrict keyword

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

shell portability: use "=" instead of "==" in test(1) expressions,
double-quote string with backslash escaped /

Add regress test for key options. ok djm@

fix testing of pty option, include positive test and testing of
restrict keyword

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

shell portability: use "=" instead of "==" in test(1) expressions,
double-quote string with backslash escaped /

Add regress test for key options. ok djm@

eliminate explicit specification of protocol in tests and loops over
protocol. We only support SSHv2 now.

make it possible to run tests w/o ssh1 support; ok djm@

shell portability: use "=" instead of "==" in test(1) expressions,
double-quote string with backslash escaped /

Add regress test for key options. ok djm@