Use '#' for host#port separator, document it. This fixes scp
in multihop
... | ... | @@ -15,7 +15,7 @@ dbclient \- lightweight SSH2 client |
.B dbclient | ||
[ | ||
.I args ] | ||
.I [user1]@host1[/port1],[user2]@host2[/port2],... | ||
.I [user1]@host1[#port1],[user2]@host2[#port2],... | ||
.SH DESCRIPTION | ||
.B dbclient | ||
... | ... | @@ -24,10 +24,9 @@ environments, while still being functional and secure enough for general use. |
.SH OPTIONS | ||
.TP | ||
.B \-p \fIport | ||
Remote port. | ||
Connect to port | ||
Connect to | ||
.I port | ||
on the remote host. | ||
on the remote host. Alternatively a port can be specified as hostname#port. | ||
Default is 22. | ||
.TP | ||
.B \-i \fIidfile | ||
... | ... | @@ -127,7 +126,7 @@ Dropbear will also allow multiple "hops" to be specified, separated by commas. I |
this case a connection will be made to the first host, then a TCP forwarded | ||
connection will be made through that to the second host, and so on. Hosts other than | ||
the final destination will not see anything other than the encrypted SSH stream. | ||
A port for a host can be specified with a slash (eg [email protected]/44 ). | ||
A port for a host can be specified with a hash (eg [email protected]#44 ). | ||
This syntax can also be used with scp or rsync (specifying dbclient as the | ||
ssh/rsh command). A file can be "bounced" through multiple SSH hops, eg | ||
... | ... |
Please register or sign in to comment