Change port separator to semicolon : since it's more standard #222
Conversation
Kindly suggesting to switch to semicolon character `:` as port separator as `[user@]hostname[:port]`. Current port separator is `^` which is less standard -- semicolon is used both in `ssh` and `scp` programs. For maintaining backward compatibility, similar to the support of legacy `/`, the character `^` can still be supported. Appendix -------- A bit of history: - From what I've been able to understand from Git history, everything started in 2008 with the usage of `/` as port separator, implemented in [1]. - Five years later, in 2013, This was changed [2] to `#` to fix a problem related to `scp`. Not sure, but a plausible reason for this could be a clash with the usage of `/` for directories. Note that the usage of `/` was still allowed as legacy. - That same year it was changed again [3] to `%` for some reason I have not been able to understand. - Then, in 2014, since `%` is used by IPv6 addresses, this was changed [4] to use `^` as port separator -- and this is the current state. As a comment, `/` is still supported as legacy. [1]: mkj@d981ff2 [2]: mkj@3525cab [3]: mkj@f98eb58 [4]: mkj@0c9a643
| @@ -205,7 +205,7 @@ in the example above, the same way as other -L TCP forwarded hosts are. Host key | |||
| checked locally based on the given hostname. | |||
|
|
|||
| .SH ESCAPE CHARACTERS | |||
| Typing a newline followed by the key sequence \fI~.\fR (tilde, dot) will terminate a connection. | |||
| Typing a newline followed by the key sequence \fI~.\fR (tilde, dot) will terminate a connection. | |||
There was a problem hiding this comment.
This was an not related typo.
| @@ -194,7 +194,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 caret (eg matt@martello^44 ). | |||
| A port for a host can be specified with a caret (eg matt@martello:44 ). | |||
There was a problem hiding this comment.
Just noticed this.
| A port for a host can be specified with a caret (eg matt@martello:44 ). | |
| A port for a host can be specified with a colon (eg matt@martello:44 ). |
|
My bad, just noticed that |
|
The syntax here is only for multihop, which OpenSSH added later with their I think the reason I avoided Line 128 in 7f80432 I can't remember exactly but assume the reason |
|
I believe the : was avoided because of the scp use for specifying the destination filename/path like scp -P port user@host:filename |
Ah yes, I think that's right. So even with |
Kindly suggesting to switch to semicolon character
:as port separator as[user@]hostname[:port]. Current port separator is^which is less standard -- semicolon is used both insshandscpprograms.For maintaining backward compatibility, similar to the support of legacy
/, the character^can still be supported.Appendix
A bit of history:
From what I've been able to understand from Git history, everything started in 2008 with the usage of
/as port separator, implemented in 1.Five years later, in 2013, This was changed 2 to
#to fix a problem related toscp. Not sure, but a plausible reason for this could be a clash with the usage of/for directories. Note that the usage of/was still allowed as legacy.That same year it was changed again 3 to
%for some reason I have not been able to understand.Then, in 2014, since
%is used by IPv6 addresses, this was changed 4 to use^as port separator -- and this is the current state.As a comment,
/is still supported as legacy.