wolfssh/examples
John Safranek 48f36f753a Reject an out-of-range -p port
The -p option of wolfssh, client, wolfscp, wolfsftp and echoserver now
goes through a strtol check, so a value that is not wholly a number in
range exits with an error instead of wrapping into a different port.

- apps/wolfssh: ClientParsePort(), shared with ClientParseDestination(),
  which also rejects an empty "ssh://host:" port instead of defaulting
- examples: a ClientParsePort() in examples/client/common.c; port 0 is
  rejected in every build, not only with a main driver
- echoserver: accepts 0 to 65535, keeping 0 for the test harness
- add TestClientParsePort and an empty URI port case to regress.test

Issue: F-14763, F-14767, F-14768, F-12552
2026-10-28 13:10:29 -05:00
..
client Reject an out-of-range -p port 2026-10-28 13:10:29 -05:00
echoserver Reject an out-of-range -p port 2026-10-28 13:10:29 -05:00
portfwd Drop the sshd and client apps with their side 2026-10-16 13:37:01 -05:00
scpclient Reject an out-of-range -p port 2026-10-28 13:10:29 -05:00
sftpclient Reject an out-of-range -p port 2026-10-28 13:10:29 -05:00
tpmcertserver Adopt the certificate loading APIs in the examples and apps 2026-08-12 16:06:39 -07:00
include.am examples: add TPM-backed X.509 host certificate server and client 2026-07-07 14:28:56 -07:00