flashproxy-client - The flash proxy client transport plugin
flashproxy-client --register [OPTIONS] [LOCAL][:PORT] [REMOTE][:PORT]
Wait for connections on a local and a remote port. When any pair of connections exists, data is ferried between them until one side is closed. By default LOCAL is localhost addresses on port 9001 and REMOTE is all addresses on port 9000.
The local connection acts as a SOCKS4a proxy, but the host and port in the SOCKS request are ignored and the local connection is always linked to a remote connection.
By default, runs as a managed proxy: informs a parent Tor process of support for the "flashproxy" or "websocket" pluggable transport. In managed mode, the LOCAL port is chosen arbitrarily instead of defaulting to 9001; however this can be overridden by including a LOCAL port in the command. This is the way the program should be invoked in a torrc ClientTransportPlugin "exec" line. Use the --external option to run as an external proxy that does not interact with Tor.
If any of the --register, --register-addr, or --register-methods options are used, then your IP address will be sent to the facilitator so that proxies can connect to you. You need to register in some way in order to get any service. The --facilitator option allows controlling which facilitator is used; if omitted, it uses a public default.
Please report using https://trac.torproject.org/projects/tor.