Moat allows users to fetch bridges from BridgeDB over a domain-fronted connection. It consists of a [meek](https://gitweb.torproject.org/pluggable-transports/meek.git/) server, some apache configs, and a BridgeDB distributor. This documentation demonstrates how it is deployed at https://bridges.torproject.org.
Moat allows users to fetch bridges from BridgeDB over a domain-fronted connection. It consists of a [meek](https://gitweb.torproject.org/pluggable-transports/meek.git/) server, some apache configs, and a BridgeDB distributor. This documentation demonstrates how it is deployed at https://bridges.torproject.org.
See the [API documentation](https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/blob/main/doc/moat.md?ref_type=heads) to use it.
## Server Setup
## Server Setup
Clients connect to moat through the meek server, which then redirects traffic locally to the BridgeDB Moat distributor. These connections are facilitated through a sequence of ProxyPass rules:
Clients connect to moat through the meek server, which then redirects traffic locally to the BridgeDB Moat distributor. These connections are facilitated through a sequence of ProxyPass rules:
...
@@ -47,3 +49,12 @@ The meek client will open a SOCKS proxy on a local port and proxy all requests t
...
@@ -47,3 +49,12 @@ The meek client will open a SOCKS proxy on a local port and proxy all requests t