[Bug 3386] [FEATURE REQUEST]Option to set client source port.

bugzilla-daemon at mindrot.org bugzilla-daemon at mindrot.org
Sun Feb 6 23:17:08 AEDT 2022


--- Comment #8 from Darren Tucker <dtucker at dtucker.net> ---
(In reply to Yasen from comment #7)
> How about using some other symbol for denoting the port? "\" for
> example?

Some options actually support an obsolete form using "/" as a separator
but we've been deprecating that because for better or worse the world
has  settled on ":" with square brackets and "/" can be misinterpreted
as a subnet specification.

Anyway, I think we could require square brackets when supplying a port.
 That would give the following semantics which would be backward
 - no colons: IPv4 or hostname
 - one colon: IPv4 and port or hostname and port
 - two or more colons and no square brackets: bare IPv6 address.
 - two or more colons and square brackets: IPv6 address and port.

I got as far as adding a unit test to make I don't break it any

You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.

More information about the openssh-bugs mailing list