Jędrzej Stuczyński
0801b3c6f8
* exit policy types * simple client for grabbing the policy * moved allowed_hosts to a submodule * started integrating exit policy into a NR * ability to construct ExitPolicyRequestFilter * fixed policy parsing to look for comment char from the left * conditionally setting up request filter * [wip] setting up correct url for exit policy upstream * clap flags for running with exit policy * fixed NR template * updated NR config template * making sure to perform request filtering in separate task * initial, placeholder, exit policy API endpoint * serving exit policy from an embedded NR * double slash sanitization * socks5 query for exit policy * adjusted address policy logging * cargo fmt * Updated exit policy url to point to the correct mainnet file * removed unecessary mutability in filter tests * fixed the code block showing example policy being interpreted as doc test
Copyright 2022 - Nym Technologies SA contact@nymtech.net SPDX-License-Identifier: Apache-2.0 -->
Network requester
The network requester is used to interpret socks5 client messages that need to be proxied to a running service i.e. a host and a port.
If you have a service that you want to expose to the mixnet, you'd need to first run the native client and provide the client address to your users that will use it in their socks5 configuration.
After starting the native client, start the network requester and configure it,
setting your service's endpoint in
${HOME}/.nym/service-providers/network-requester/allowed.list
Running in open-proxy mode allows any traffic to be proxied by the network
requester.
Statistics service
The network requester can be ran as a gatherer of statistics for all
the services it proxies. For that, run the binary with the
enable-statistics flag enabled. Anonymized statistics are then sent to
a central server, through the mixnet.