|
1 | | -``` |
2 | 1 | @@@@@ |
3 | 2 | @@@@@@@@@@@@@@@@@ |
4 | 3 | @@@@@@@@@@@@@@@ @@@@@ |
|
33 | 32 | - [Configuration](#configuration) |
34 | 33 | - [Security Levels](#security-levels) |
35 | 34 | - [Advanced Tor Configuration](#advanced-tor-configuration) |
| 35 | + - [Vanguards Configuration](#vanguards-configuration) |
36 | 36 | - [Building from Source](#building-from-source) |
37 | 37 | - [Installing Prerequisites](#installing-prerequisites) |
38 | 38 | - [Building Standard Image](#building-standard-image) |
@@ -360,6 +360,61 @@ WarnUnsafeSocks 1 |
360 | 360 |
|
361 | 361 | > **Note**: When using a custom torrc file, make sure it includes the line `# PORTS` where the port configurations should be inserted. Port mappings are dynamically generated from the `TOR_SERVICE_PORTS` environment variable. |
362 | 362 |
|
| 363 | +### Vanguards Configuration |
| 364 | + |
| 365 | +OnionDock includes a pre-configured `vanguards.conf` with balanced security settings. For high-risk services like whistleblower sites or sites facing state-level adversaries, we provide a maximum security configuration in `vanguards-max-security.conf`. |
| 366 | + |
| 367 | +**To use maximum security settings:** |
| 368 | +```bash |
| 369 | +# When using your own volume mounts |
| 370 | +cp tor/config/vanguards-max-security.conf tor/config/vanguards.conf |
| 371 | +``` |
| 372 | + |
| 373 | +**Key Configuration Parameters:** |
| 374 | + |
| 375 | +- **[Global]** |
| 376 | + - `control_ip`: Tor control connection IP (default: 127.0.0.1) |
| 377 | + - `control_socket`: Path to Unix socket for Tor control (empty = use IP+port instead) |
| 378 | + - `control_pass`: Password for Tor control authentication (empty = cookie auth) |
| 379 | + - `enable_logguard`: Enables logging protection (true/false) |
| 380 | + - `close_circuits`: Automatically closes suspicious circuits |
| 381 | + - `enable_pathverify`: Verifies path selection to detect manipulation |
| 382 | + - `one_shot_vanguards`: Regenerates guards on restart |
| 383 | + - `loglevel`: Log verbosity level (NOTICE, INFO, DEBUG) |
| 384 | + |
| 385 | +- **[Vanguards]** |
| 386 | + - `layer1_lifetime_days`: How often to rotate entry guards (lower = more secure) |
| 387 | + - `max_layer2_lifetime_hours`: Maximum time to keep middle-layer guards |
| 388 | + - `max_layer3_lifetime_hours`: Maximum time to keep exit-layer guards |
| 389 | + - `min_layer2_lifetime_hours`: Minimum time before replacing middle-layer guards |
| 390 | + - `min_layer3_lifetime_hours`: Minimum time before replacing exit-layer guards |
| 391 | + - `num_layer1_guards`: Number of entry guards (more = more secure) |
| 392 | + - `num_layer2_guards`: Number of middle-layer guards (more = more secure) |
| 393 | + - `num_layer3_guards`: Number of exit-layer guards (more = more secure) |
| 394 | + |
| 395 | +- **[Bandguards]** |
| 396 | + - `circ_max_age_hours`: Maximum circuit lifetime (lower = more secure) |
| 397 | + - `circ_max_hsdesc_kilobytes`: Maximum descriptor download size before circuit closure |
| 398 | + - `circ_max_serv_intro_kilobytes`: Maximum intro point traffic before circuit closure |
| 399 | + - `circ_max_megabytes`: Bandwidth limits for circuits (lower = more secure) |
| 400 | + - `circ_max_disconnected_secs`: Closes circuits after this many seconds of disconnection |
| 401 | + - `conn_max_disconnected_secs`: Closes connections after this many seconds of disconnection |
| 402 | + |
| 403 | +- **[Rendguard]** |
| 404 | + - `rend_use_max_use_to_bw_ratio`: Limits excessive use of rendezvous points |
| 405 | + - `rend_use_max_consensus_weight_churn`: Limits changes in consensus weight |
| 406 | + - `rend_use_close_circuits_on_overuse`: Closes circuits when rendezvous points are overused |
| 407 | + - `rend_use_global_start_count`: Minimum consensus count before enabling protections |
| 408 | + - `rend_use_relay_start_count`: Minimum relay consensus count before monitoring |
| 409 | + - `rend_use_scale_at_count`: Consensus count threshold for scaling protection |
| 410 | + |
| 411 | +- **[Logguard]** |
| 412 | + - `log_protocol_warns`: Enables warning on protocol anomalies |
| 413 | + - `log_dump_limit`: Maximum number of log lines to dump on anomaly detection |
| 414 | + - `log_dump_level`: Verbosity of logs (NOTICE or DEBUG in max security) |
| 415 | + |
| 416 | +> **Security Note**: High-risk services like whistleblower sites, dissident platforms, or sites facing state-level adversaries should use the max security configuration. This offers significantly stronger protection against sophisticated attackers at the cost of some performance. |
| 417 | +
|
363 | 418 | ## Building from Source |
364 | 419 |
|
365 | 420 | If you prefer to build the OnionDock images locally rather than using the pre-built Docker Hub images, follow these instructions. |
|
0 commit comments