PG-RSCA-2526-TorAttack/experiment-infra/README.md
2025-06-02 10:25:48 +02:00

36 lines
1.3 KiB
Markdown

# Tor Experiment Infrastructure
## Available Systems
| IP | Domain | Location | Purpose |
|---:|:-------|:---------|:--------|
| 164.90.190.0 | rsca.vanrissenbeck.com | Frankfurt | Host a webservice, take measurements. |
| 95.85.53.75 | n.a. | Amsterdam | Host a private Tor guard node |
| 64.225.67.64 | n.a. | Amsterdam | Host a private Tor guard node |
## Containers
The `guard` container provides a single guard node, configured so that it
does not announce its IP to public indices. The container is configured
by two environment variables, `BIND_ADDRESS` and `NICKNAME`. The values
in the associated `docker-compose.yml` file are fine as they are.
kept in the `
The `victim` container provides the Tor service configured as a SOCKS5
proxy. It connects to one hard-coded guard node, specified using the
environment variable `GUARD`.
Both containers are stored in the `ghcr.io` registry under the tags
`ghcr.io/deinernstjetzt/rsca-guard` or `ghcr.io/deinernstjetzt/rsca-victim`
respectively.
The `web` container provides a simple web server (Caddy) that serves static files from the `www` directory. Large test files can be downloaded from [Hetzner](https://ash-speed.hetzner.com/).
## Exposed Ports
| Name | Host:Port |
|:---------|------------------|
| Guard #1 | 95.85.53.75:30720 |
| Guard #2 | 64.225.67.64:62268 |
| Web | 164.90.190.0:{80,443} |