proxychains(1)proxychains(1)NAME
ProxyChains - redirect connections through proxy servers
SYNTAX
proxychains <program>
DESCRIPTION
This program forces any tcp connection made by any given tcp client to follow through proxy (or proxy chain). It is a kind of proxifier.
It acts like sockscap / premeo / eborder driver (intercepts TCP calls).
This version (2.0) supports SOCKS4, SOCKS5 and HTTP CONNECT proxy servers. Auth-types: socks - "user/pass" , http - "basic".
When to use it ?
1) When the only way to get "outside" from your LAN is through proxy server.
2) When you are behind restrictive firewall which filters outgoing connections to some ports.
3) When you want to use two (or more) proxies in chain:
like: your_host <--> proxy1 <--> proxy2 <--> target_host
4) When you want to "proxify" some programs with no proxy support built-in (like telnet).
5) When you dont want to pay for eBorder / premeo socks driver :)
Some cool features:
* This program can mix different proxy types in the same chain
like: your_host <-->socks5 <--> http <--> socks4 <--> http <--> target_host
* Different chaining options supported like: take random proxy from the list. or : chain proxies in exact order or :
chain proxies in dynamic order (smart exclude dead proxies from chain)
*You can use it with any TCP client application, even network scanners. yes, yes - you can make portscan via proxy (or chained proxies) for
example with Nmap scanner by fyodor (www.insecure.org/nmap).
proxychains nmap -sT -PO -p 80 -iR (find some webservers through proxy)
NOTE: to run suid/sgid programs(like ssh) through proxychains you have to be root
FILES
proxychains looks for config file in following order:
./proxychains.conf
$(HOME)/.proxychains/proxychains.conf
/etc/proxychains.conf
see more in /etc/proxychains.conf
EXAMPLES
To run this program the standard way type:
proxychains telnet targethost.com
in this example it will run telnet through proxy(or chained proxies) specified by proxychains.conf
COPYING
proxychains is distributed under the GNU General Public License. (GPL 2.0 or greater).
AUTHORS
Net Creature, Proxy Labs
<http://proxychains.sourceforge.net>
<Net Creature> 2.0 proxychains(1)
Check Out this Related Man Page
Net::Proxy::Connector::connect_ssl(3pm) User Contributed Perl Documentation Net::Proxy::Connector::connect_ssl(3pm)NAME
Net::Proxy::Connector::connect_ssl - Create SSL/CONNECT tunnels through HTTP proxies
SYNOPSIS
# sample proxy using Net::Proxy::Connector::tcp
# and Net::Proxy::Connector::connect_ssl
use Net::Proxy;
# listen on localhost:6789
# and proxy to remotehost:9876 through proxy.company.com:8080
# using the given credentials
my $proxy = Net::Proxy->new(
in => { type => 'tcp', port => '6789' },
out => {
type => 'connect_ssl',
host => 'remotehost',
port => '9876',
proxy_host => 'proxy.company.com',
proxy_port => '8080',
proxy_user => 'jrandom',
proxy_pass => 's3kr3t',
proxy_agent => 'Mozilla/4.04 (X11; I; SunOS 5.4 sun4m)',
},
);
$proxy->register();
Net::Proxy->mainloop();
DESCRIPTION
"Net::Proxy::Connecter::connect_ssl" is a "Net::Proxy::Connector" that uses the HTTP CONNECT method to ask the proxy to create a tunnel to
an outside server. The data is then encrypted using SSL.
Obviously, you'll need a server that understands SSL (or a proxy using "Net::Proxy::Connector::ssl") at the other end.
This connector is only an "out" connector.
In addition to the options listed below, this connector accepts all "SSL_..." options to "IO::Socket::SSL". They are transparently passed
through to the appropriate "IO::Socket::SSL" methods when upgrading the socket to SSL.
CONNECTOR OPTIONS
"Net::Proxy::Connector::connect" accepts the following options:
"out"
o host
The destination host.
o port
The destination port.
o proxy_host
The web proxy name or address.
o proxy_port
The web proxy port.
o proxy_user
The authentication username for the proxy.
o proxy_pass
The authentication password for the proxy.
o proxy_agent
The user-agent string to use when connecting to the proxy.
AUTHOR
Philippe 'BooK' Bruhat, "<book@cpan.org>".
HISTORY
Because "Net::Proxy" blocks when it tries to connect to itself, it wasn't possible to pass an SSL-encrypted connection through a proxy with
a single script: you needed one for the SSL encapsulation, and another one for bypassing the proxy with the "CONNECT" HTTP method.
See "Net::Proxy::Connector::connect" and "Net::Proxy::Connector::ssl" for details.
COPYRIGHT
Copyright 2007 Philippe 'BooK' Bruhat, All Rights Reserved.
LICENSE
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.10.1 2009-10-18 Net::Proxy::Connector::connect_ssl(3pm)