openssh unix dev - Mar 2014 - ProxyCommand as both a resolver and connector

I see that the hostname canonicalization configuration options is still
rather limited. As that works on DNS level they are of not use if one has
to use ProxyCommand to connect over a proxy connection or through a common
gateway name where one uses different port numbers to connect to different
intranet names.

What would be ideal is to extend the ProxyCommand to both return the
resolved universal name for the given short name and to connect to that
universal name. For example, the proxy can first print the resolved name on
its stdout before proceeding with other data.

On Sun, 23 Mar 2014, Igor Bukanov wrote:
> I see that the hostname canonicalization configuration options is still
> rather limited. As that works on DNS level they are of not use if one has
> to use ProxyCommand to connect over a proxy connection or through a common
> gateway name where one uses different port numbers to connect to different
> intranet names.
> 
> What would be ideal is to extend the ProxyCommand to both return the
> resolved universal name for the given short name and to connect to that
> universal name. For example, the proxy can first print the resolved name on
> its stdout before proceeding with other data.
It's an interesting idea, probably best used in conjunction with the fd-
passing proxy mode. I don't know if I'm interested enough to implement
it
myself, but you should file an enhancement bug at
https://bugzilla.mindrot.org so it doesn't get lost.

-d