[FreeNX-kNX] how to direct the NX client through an HTTP proxy?

[Kurt Pfeifle]

On Saturday 27 August 2005 03:37, Kirk Wurffell wrote:

>   My client machine is behind a proxy/firewall and I'm only allowed to reach 
> the outside world through this proxy and a specific port.

I'm in the same situation, often.

I use "transconnect" to overcome this. (http://transconnect.sf.net/)

What it provides:
-----------------
transconnect can make most applications proxy-aware (those which are 
compiled non-statically and which use the libc), even if they are not
designed to use a proxy.

How it works:
-------------
transconnect consists of two files: the tconn.so mini library, and a 
configuration file, tconn.conf. tconn.so is pre-loaded (use f.e. the
commandline "LD_PRELOAD=/usr/lib/tconn.so  /usr/NX/bin/nxclient" to
start the NX client). The tconn.so intercepts all CONNECT requests and
hands these to the proxy. The tconn.conf file holds the actual proxy
data, including the proxy authentication (should it be required).

Where the limitations are:
--------------------------
The proxy must be configured to forward the connection to the required 
port. (I sometimes find proxies who only forward outgoing connections
with target ports 80 or 443. In these cases it always helped to have 
the SSH daemon on the NX server to also listen on 443; transconnect
will then ask to proxy to forward to 443, the proxy will do this, and
on 443 the target's sshd will receive the connection request and handle
it).

Cheers,
Kurt