RemoteForward and dynamically allocated listen port

[Alex Bligh]

On 5 Aug 2013, at 20:04, Andrew Pimlott wrote:

> Specifying a RemoteForward of 0:example.com:1234 dynamically allocates
> the listen port on the server, and then reports it to ... the client!
> Where it is practically useless.  Was this someone's idea of a joke?

Yes this is not great; I've wanted this too.

One problem with your approach is that the child may already be running
by the time the remote forward is processed; that could be ten minutes
after the session start.

-- 
Alex Bligh