[Network contribution] Implements a "proxy" for reverse shell

[mauricelambert]

Some times we can't established communication between target's servers and your own computer, but it's possible to spawn a reverse shell on other server than have access to the target's servers. So the easiest way to spawn a reverse shell on the target and control it from your computer is a "proxy" reverse shell. We probably need to implements this "proxy" with multiple incoming protocols (to bypass the first firewall) and multiple outbound protocols (to bypass a second firewall), so the "proxy" should "translate" packets (the command in the content) from a protocol to another protocol.

[mauricelambert]

I add TCP, UDP, and multi-TCP bridge. This tools can be used as a simple "gateway" to send payload from a pwned server to another, it's useful to pwn a server with indirect network access (to pwn a second server in the first pwned server local network).

This is not a ReverseShell "proxy" (or "gateway") to use a protocol for the first connection and another protocol for the second connection. (For example use HTTPS to send payloads in the DMZ (on pwned Web server), when firewall accept output connection on port 443 with SSL, and use DNS to send payloads from DMZ to production environment, when firewall do not accept HTTPS between DMZ and production but accept DNS).