FullProxy
Bind and reverse connection based, SOCKS5, HTTP and PortForward proxy.
Description
FullProxy is a Bind and Reverse Connection based HTTP, SOCKS5 and PortForward portable proxy
Index
Usage
Implemented protocols
user@linux:~$ fullproxyOutputs:
path/to/fullproxy MODE NETWORK_TYPE ADDRESS PROTOCOL [OPTIONS]
- MODE: bind|master|slave
- NETWORK_TYPE: tcp|udp
- ADDRESS: IPv4|IPv6 or Domain followed by ":" and the PORT; For Example -> "127.0.0.1:80"
- PROTOCOL: socks5|http|port-forward|translate-socks5
Environment Variables:
- C2Address Host and port of the C2 port of the master server
SOCKS5
user@linux:~$ fullproxy bind tcp 127.0.0.1:9050 socks5 --helpOutputs:
Usage of socks5:
-auth-cmd string
shell command to pass the hex encoded username and password, exit code 0 means login success
-inbound-blacklist string
plain text file list with all the HOST that are forbidden to connect to the proxy
-inbound-whitelist string
plain text file list with all the HOST that are permitted to connect to the proxy
-outbound-blacklist string
plain text file list with all the forbidden proxy targets
-outbound-whitelist string
plain text file list with all the permitted proxy targets
-users-file string
json file with username as keys and sha3-513 of the password as valuesHTTP
HTTP proxy could be implemented thanks to goproxy
user@linux:~$ fullproxy http -helpOutputs:
Usage of http:
-auth-cmd string
shell command to pass the hex encoded username and password, exit code 0 means login success
-inbound-blacklist string
plain text file list with all the HOST that are forbidden to connect to the proxy
-inbound-whitelist string
plain text file list with all the HOST that are permitted to connect to the proxy
-outbound-blacklist string
plain text file list with all the forbidden proxy targets
-outbound-whitelist string
plain text file list with all the permitted proxy targets
-users-file string
json file with username as keys and sha3-513 of the password as valuesPort Forward
user@linux:~$ fullproxy bind tcp 127.0.0.1:9050 port-forward --helpOutputs
Usage of port-forward:
-inbound-blacklist string
plain text file list with all the HOST that are forbidden to connect to the proxy
-inbound-whitelist string
plain text file list with all the HOST that are permitted to connect to the proxy
-network-type string
tcp or udp (default "tcp")
-target-address string
Address to connect (default "127.0.0.1:80")Master and Slave
Preparing the master
Serve a socks5 proxy using master and slave.
user@linux:~$ export C2Address="127.0.0.1:9051" && fullproxy master tcp 127.0.0.1:9050 socks5 [OPTIONS]Preparing the slave
Connect to the master and proxy the networks from the slave side.
user@linux:~$ export C2Address="127.0.0.1:9051" && fullproxy slave tcp 127.0.0.1:9050 socks5Implemented tools
fullproxy-users
This tool will create a valid JSON file to use with the flag -users-file
user@linux:~$ fullproxy-usersOutputs:
fullproxy-users COMMAND DATABASE_FILE USERNAME
Available commands:
- new
- delete
- setCommands:
new
Creates a new file with a new user.
delete
Deletes an existing user in the file.
set
Creates or updates a user in the file.
Concepts
Master/Slave
Handles the proxying between a reverse connected proxy and the clients. In other words, it will receive the connections of the clients and will forward the traffic to the proxy that is reverse connected to it.
How it works
- It first binds to the host specified by the user.
- Then accept the connection from the proxy server.
- Finally, it proxy the traffic of all new incoming connections to the proxy server that was reverse connected to it in the second step. In other words, is the proxy of another proxy but totally invisible for the client.
Applications
This could be specially useful when you need to proxy a network that a machine have access to, but you can't bind inside that machine.
Installation
Pre-compiled binaries
You can find pre-compiled binaries for windows and linux Here
Build from source code
fullproxy
go install github.com/shoriwe/FullProxy/v2/cmd/fullproxy@latestfullproxy-users
go install github.com/shoriwe/FullProxy/v2/cmd/fullproxy-users@latestNote
For some reason (possibly a coding fault commit by me) if you extremely stress the master/slave protocol, it will crash in away that it is still running and the new connections are received but the connections to the targets are never made.