A Tiny free proxy server.
Unix
Windows
--install as service--remove as serviceWindows 95/98/ME
--install as service--remove as serviceCombined proxy server may be used as executable or service (supports installation and removal). It uses config file to read it’s configuration (see 3proxy.cfg.sample for details). 3proxy.exe is an all-in-one, it doesn’t require additional executables to work. See 3proxy.cfg.sample for examples, see man 3proxy.cfg.
| Function | Description |
|—|———|
| proxy | HTTP proxy server, binds to port 3128 |
| ftppr | FTP proxy server, binds to port 21 |
| socks | SOCKS 4/5 proxy server, binds to port 1080 |
| ftppr | FTP proxy server, please do not mess it with FTP over HTTP proxy used in browsers |
| pop3p | POP3 proxy server, binds to port 110. You must specify POP3 username as username@target.host.ip[:port] port is 110 by default. Example: in Username configuration for you e-mail reader set someuser@pop.example.org, to obtains mail for someuser from pop.somehost.ru via proxy. |
| smtpp | SMTP proxy server, binds to port 25. You must specify SMTP username as username@target.host.ip[:port] port is 25 by default. Example: in Username configuration for you e-mail reader set someuser@mail.example.org, to send mail as someuser via mail.somehost.ru via proxy. |
| tcppm | TCP port mapping. Maps some TCP port on local machine to TCP port on remote host. |
| udppm | UDP port mapping. Maps some UDP port on local machine to UDP port on remote machine. Only one user simulationeously can use UDP mapping, so it cann’t be used for public service in large networks. It’s OK to use it to map to DNS server in small network or to map Counter-Strike server for single client (you can use few mappings on different ports for different clients in last case). |
| mycrypt | Program to obtain crypted password fro cleartext. Supports both MD5/crypt and NT password. |
mycrypt password
produces NT password
mycrypt salt password
produces MD5/crypt password with salt “salt”.
Instructions on how to install the tool or package on BlackArch Linux.
pacman -S 3proxy
/etc/3proxy/conf/add3proxyuser.sh <username> <password> [day_limit] [bandwidth]
day_limit - traffic limit in MB per day.
bandwidth - bandwidth in bits per second 1048576 = 1mbps
or modify /etc/3proxy/conf/ files directly.
Docker images here
2 docker configurations are provided, defaul (full) and :minimal for devel and stable 3proxy versions. :latest is a full configuration for stable version.
Default configuration:
Dockerfile with fully dunctional busibox:glibc based 3proxy installation, requires mounting configuration file.
To build:
docker build -f Dockerfile.full -t 3proxy
To run:
By default 3proxy uses safe chroot environment with chroot to /usr/local/3proxy with uid/gid 65535/65535 and expects configuration file to be placed in /usr/local/etc/3proxy. Paths in configuration file must be relative to /usr/local/3proxy, that is use /logs instead of /usr/local/3proxy/logs. nserver in chroot is required for DNS resolution.
Example:
echo nserver 8.8.8.8 >/path/to/local/config/directory/3proxy.cfg
echo proxy -p3129 >>/path/to/local/config/directory/3proxy.cfg
docker run -p 3129:3129 -v /path/to/local/config/directory:/usr/local/3proxy/conf -name 3proxy.full 3proxy
/path/to/local/config/directory in this example must contain 3proxy.cfg if you need 3proxy to be executed without chroot with root permissions, replace /etc/3proxy/3proxy.cfg by e.g. mounting config dir to /etc/3proxy or by providing config file /etc/3proxy/3proxy.cfg
docker run -p 3129:3129 -v /path/to/local/config/directory:/etc/3proxy -name 3proxy 3proxy
use log without pathname in config to log to stdout or mount volume for logs. plugins are located in /usr/local/3proxy/libexec (/libexec for chroot config). Some proxy types (e.g. SOCKSv5 UDPASSCOC, SOCKSv5 BIND functionality, ftp proxy) require access to ephemeral port, you may use e.g. --network host mode or -P for docker run.
This is busybox based docker with only 3proxy executable and empty non-writable “run” directory.
plugin is not supported.
Build:
docker build -f Dockerfile.minimal -t 3proxy.minimal
Run example:
docker run -i -p 3129:3129 --name 3proxy 3proxy.minimal or docker start -i 3proxy
send this to standard input (example):
chroot run 65535 65535
nserver 8.8.8.8
nscache 65535
log
proxy -p3129
end
Use chroot run 65536 65536 in config for safe chroot environment. nserver is required for DNS resolutions in chroot.
Some proxy types (e.g. SOCKSv5 UDPASSCOC, SOCKSv5 BIND functionality, ftp proxy) require access to ephemeral port, you may use e.g. --network host mode or -P to docker run.
:minimal without version specified uses current stable version.
It is important to note that the use of this tool for any illegal or unauthorized activities is strictly prohibited. The creators of this tool and BlackArch Linux will not be held liable for any actions taken with its use. This tool is intended for use by security professionals and researchers for lawful and ethical testing purposes only. Remember, always obtain proper authorization and comply with all relevant laws and regulations when using this tool or any other security tool.