Matt Johnston wrote:
> Adding unspecified-port remote forwarding would probably be
> fairly straightforward - I just didn't see a need for it
> previously.
I need some hints about implementing remote port forwarding
w/o specifying a remote port on the client side:
I know already how to handle t
Matt Johnston wrote:
> Neither client-ip nor the YY port are given to the remote
> server in the SSH_MSG_GLOBAL_REQUEST packet. I don't quite
> see how it would be useful though?
The need in my (special) case would be to be able to provide
a web-application with a list of only those URLs which ar
On Mon, Nov 03, 2008 at 07:52:14AM +0100, Michael Wiedmann wrote:
> Hi,
>
> am I correct, that the local port used on the client ('YY' in '-R
> :client-ip:YY') is not part of the SSH_MSG_GLOBAL_REQUEST packet (see
> http://www.faqs.org/rfcs/rfc4254.html, 7.1. Requesting Port Forwarding)?
>
Hi,
am I correct, that the local port used on the client ('YY' in '-R
:client-ip:YY') is not part of the SSH_MSG_GLOBAL_REQUEST packet (see
http://www.faqs.org/rfcs/rfc4254.html, 7.1. Requesting Port Forwarding)?
I'd like to know on the server side (child process) the port the clients wish
