SocksFusion is a utility for creating an encrypted connection ("tunnel") to allow passing TCP messages through a firewall. SocksFusion consists of two components: the Agent (freely downloadable application) and the Proxy (BlackBox Scanner service).
Network connection diagram:
+-----------+
| BBS Cloud |
+-----------+
^
NAT |
+--------+ +-------+ | | +-------+ +--------+
| Target | <------ | Agent | ----|-|---> | Proxy | <------ | Client |
+--------+ +-------+ | | +-------+ +--------+
The agent is a client application that forwards requests from the scanner. When launched, it connects with the proxy, performs a handshake, and sends its token. If authorization is successful, you can start scanning via the agent. The agent listens to the proxy and responds to requests in accordance with Socks5.
Usage: Agent [string] [-a|--api URL] [--tutorial] [-s|--skip] [-i|--insecure]
[-d|--debug] [-o|--once] [--token-path filepath]
[-p|--proxy host:port] [--token string] [-v|--version]
Available options:
string Specify activation code
-a,--api URL Use indicated API server address
--tutorial Run interactive tutorial
-s,--skip Use default configuration
-i,--insecure Keep going if SSL certificate cannot be verified
-d,--debug Show packet debugging information
-o,--once Exit when scanning completes
--token-path filepath Use indicated path to read/write token
-p,--proxy host:port Use indicated proxy server
--token string Use indicated token
-v,--version Show agent version
-h,--help Show this help text
The proxy is the server responsible for connecting agents and clients (scanner instances). The proxy makes the Socks5 interface available to client applications.
The token is a random string used for authorization of a particular agent. If the agent is unable to read the token from the command line or from file, get a new one from the API server with your activation code. By default, the token is stored in %APP_DATA%/bbs/RemoteAgent.token (Windows) or $HOME/.bbs/RemoteAgent.token (Linux).