2015-03-31 03:05 AEST by Glen Starrett - The ssh protocol ignores the port setting.

On test system PLUTO (IP 192.168.1.30), only port 22 is listening for incoming
ssh.  All these command still work, even though they shouldn't with the port
being set on the command line:


>cvs -d :ssh:gstarret@pluto:2324:/test ls hello9b/sub2
Listing module: hello9b/sub2

test5.txt
test6.txt

>cvs -d :ssh;port=2332:gstarret@pluto:/test ls hello9b/sub2
Listing module: hello9b/sub2

test5.txt
test6.txt

>cvs -d :ssh;port=321:gstarret@192.168.1.30:/test ls hello9b/sub2
Listing module: hello9b/sub2

test5.txt
test6.txt

>cvs -d :ssh:gstarret@192.168.1.30:321:/test ls hello9b/sub2
Listing module: hello9b/sub2

test5.txt
test6.txt


Note that the client has a putty profile for "Pluto UTF-8", but none for "Pluto"
nor "192.168.1.30".

Also note that I have NOT tested for the case where the ssh listening port is
actually changed and the command attempts to connect to the changed port.  It is
POSSIBLE this is a fallback behavior.  E.g. if the connection to the 'forced'
port fails, fall back to port 22 and try that.