mirror of
https://github.com/proxytunnel/proxytunnel.git
synced 2026-01-23 10:36:13 +00:00
No description
compiling using gcc would conflict (it attempts to g++ compile Makefile.cc) git-svn-id: https://proxytunnel.svn.sourceforge.net/svnroot/proxytunnel/trunk/proxytunnel@60 bc163920-b10d-0410-b2c5-a5491ca2ceef |
||
|---|---|---|
| contrib | ||
| debian | ||
| _copyright.inc | ||
| base64.c | ||
| base64.h | ||
| basicauth.c | ||
| basicauth.h | ||
| CHANGES | ||
| cmdline.c | ||
| cmdline.h | ||
| config.h | ||
| CREDITS | ||
| http.c | ||
| io.c | ||
| io.h | ||
| LICENSE.txt | ||
| Makefile | ||
| Makefile.cygwin | ||
| Makefile.darwin | ||
| Makefile.no-gcc | ||
| Makefile.no-gnu-getopts | ||
| Makefile.solaris | ||
| messages.c | ||
| proxytunnel.c | ||
| proxytunnel.h | ||
| README | ||
----------- proxytunnel ----------- Author: Jos Visser <josv@osp.nl>, Mark Janssen <maniac@maniac.nl> Date: Thu Sep 30 11:22:03 CEST 2004 Version: 1.2.0 Hi all, This is proxytunnel, a program that connects stdin and stdout to an origin server somewhere in the Internet through an industry standard HTTPS proxy. I originally wrote this program to be used as an extension to SSH, to be able to SSH to my box at home. In this file, I will describe the use with SSH. If you want to use it with some other application, feel free, and let me know! Usage: Proxytunnel is very easy to use, when running proxytunnel with the help option it specifies it's command-line options. $ ./proxytunnel --help Proxytunnel 1.2.0 Jos Visser (Muppet) <josv@osp.nl>, Mark Janssen (Maniac) <maniac@maniac.nl> Purpose: Build generic tunnels trough HTTPS proxy's, supports HTTP authorization Usage: Proxytunnel [OPTIONS]... -h --help Print help and exit -V --version Print version and exit -i --inetd Run from inetd (default=off) -a INT --standalone=INT Run as standalone daemon on specified port -u STRING --user=STRING Username to send to HTTPS proxy for auth -s STRING --pass=STRING Password to send to HTTPS proxy for auth -U STRING --uservar=STRING Env var with Username for HTTPS proxy auth -S STRING --passvar=STRING Env var with Password for HTTPS proxy auth -g STRING --proxyhost=STRING HTTPS Proxy host to connect to -G INT --proxyport=INT HTTPS Proxy portnumber to connect to -d STRING --desthost=STRING Destination host to built the tunnel to -D INT --destport=INT Destination portnumber to built the tunnel to -H STRING --header=STRING Add STRING to HTTP headers sent to proxy -n --dottedquad Convert destination hostname to dotted quad -v --verbose Turn on verbosity (default=off) -q --quiet Suppress messages (default=off) Examples: Proxytunnel [ -h | -V ] Proxytunnel -i [ -u user -s pass ] -g host -G port -d host -D port [ -n ] [ -v | -q ] Proxytunnel -i [ -U envvar -S envvar ] -g host -G port -d host -D port [ -n ] [ -v | -q ] Proxytunnel -a port [ -u user -s pass ] -g host -G port -d host -D port [ -n ] [ -v | -q ] To use this program with OpenSSH to connect to a host somewhere, create a $HOME/.ssh/config file with the following content: Host foobar ProtocolKeepAlives 30 ProxyCommand /path/to/proxytunnel -g proxy.customer.com -G 8080 -u user -s password -d mybox.athome.nl -D 443 With: - foobar The symbolic name of the host you want to connect to - proxy.customer.com The host name of the proxy you want to connect through - 8080 The port number where the proxy software listens to - user Your proxy userid - password Your proxy password - mybox.athome.nl The hostname of the box you want to connect to (ultimately) - 443 The port number of the SSH daemon on mybox.athome.nl If your proxy doesn't require the username and password for using it, you can skip these options. If you are on a 'shared' system it's recommendable to store your proxy user/password data in environment variables and then tell proxytunnel which variables to check for this data. If you want to run proxytunnel from inetd add the '--inetd' option. If you have a broken proxy and use a destination host with dynamic DNS, add the -n or --dottedquad, the DNS name will then be resolved locally before sending it to the proxy. (Original patch from Ralph Loader <suckfish@ihug.co.nz>) Most HTTPS proxies do not allow access to ports other than 443 (HTTPS) and 563 (SNEWS), so some hacking is necessary to start the SSH daemon on the required port. (On the server side add an extra Port statement in the sshd_config file) When all this is in place, execute an "ssh foobar" and you're in business! Share and Enjoy! Jos Visser <josv@osp.nl> Mark Janssen <maniac@maniac.nl>