ProxyCorridor

Still under development...(aborted :()

Principle

ProxyCorridor is a program that allows you to overstep confines imposed by company's proxy.
Here are what you can do with ProxyCorridor :

Etablish a TCP connexion from your company's computer : TELNET, VNC, IRC, ...
Access to web pages normaly filtered by the proxy.

ProxyCorridor can be used as two diffrent ways. In both ways, you need a remote computer on the server side.

1. TCP Client Application behing a web proxy.

With ProxyCorridor you can use IRC, VNC (Remote access), POP3, SMTP.

2. Full Web Access through a web proxy.

With ProxyCorridor you can access the full web.

Requirements

Client side
- .Net Framework 2.0.
- Windows XP SP2, Windows 2003 Server, or Windows Vista are needed with -openproxy option.
Server side
- .Net Framework 2.0.
- Windows XP SP2, Windows 2003 Server, or Windows Vista.

Use

Server side
That should absolutely run ProxyCorridor on a remote computer (home computer).

-c (-corridor-uri) : Uri used by ProxyCorridor to establish the tunnel. This uri must be the same on the two sides.

-h (-server-host) : Host adresse of your TCP server application.
-p (-server-port) : Tcp port of your TCP server application.

-debug on : Print some connection details...
Client side
Computer at office behind company's web proxy (with NTLM authentification). On this side, ProxyCorridor use is optional.
- If you can't run ProxyCorridor, you will not be able to establish TCP connexion. On the other hand, you can have full access to web by prefixing in your browser URL as following :
  - http://myhome.dyndns.org:443/corridor/http/URL(*)
  - http://myhome.dyndns.org:443/corridor/ftp/URL(*)
  - http://myhome.dyndns.org:443/corridor/test (URL DE TEST)(*)
- If you can run ProxyCorridor, web access must be easier by replacing in your browser company's proxy server address by the one chosen with -openproxy-uri option.
-c (-corridor-uri) : Uri used by ProxyCorridor to establish the tunnel. This uri must be the same on the two sides.

-u (-proxy-uri) : Uri of the company's proxy you want to pass through.

-n (-proxy-username) : Your username if proxy needs an authentification.
-w (-proxy-password) : Your password for authentification.
-d (-proxy-domain) : Your domain for NTLM authentification.

-t (-listener-port) : Tcp port on which the TcpListener will listen on.

-o (-openproxy-uri) : Uri on which ProxyCorridor will listen on to web request. This option must not be used for tunneling tcp connection.

-debug on : Print some connection details...

Samples

VNC with ProxyCorridor

On Client Side :

1) Start ProxyCorridor :

C:\>proxyCorridor -c http://myhome.dyndns.org:443/corridor/ -t 5900 -u http://proxy.compagny.com:8080/ -n employee1 -w 78sdf98a -d company

2) Start VNC Client Application :
VNC Client must connect to proxyCorridor, so you have to type 127.0.0.1 or (localhost) in your vnc client.

On Server Side :

1) Start VNC Server...
2) Start ProxyCorridor :

C:\>proxyCorridor -c http://myhome.dyndns.org:443/corridor/ -h 127.0.0.1 -p 5900

Full Web access with ProxyCorridor

On Client Side :

1) Start ProxyCorridor :

C:\>proxyCorridor -c http://myhome.dyndns.org:443/corridor/ -o http://*:8080/ -u http://proxy.compagny.com:8080/ -n employee1 -w 78sdf98a -d company

2) Start your browser :
Configure your browser so that it can connect to proxyCorridor (it's the new proxy) : proxy address : 127.0.0.1, port : 8080

On Server Side :

1) Start ProxyCorridor :

C:\>proxyCorridor -c http://myhome.dyndns.org:443/corridor/

(*) : You can replace everywhere http://myhome.dyndns.org:443/ by http://209.85.129.104:443/ if your home public IP is 209.85.129.104... If your IP is dynamic, think about using dynamic DNS solution (DynDNS)