Files
AuraVPN/config/client.toml.example
T
xah30 fe618b839d feat(cli): v3.1 multi-hop runtime — circuit client + relay rendezvous
Completes v3.1 multi-hop / onion routing (2 hops: client → entry-relay →
exit-server). Combined with the scaffold commit (6c14c0d), the property
holds: entry-relay knows the client IP + client_id but cannot decrypt the
data; exit knows the destination but sees the relay's IP as source.

- aura-cli::circuit: dial_circuit(&[entry, exit], proto_cfg, udp_opts) →
  CircuitConnection. Connects to entry as a normal UdpClient, sends an
  ExtendBridge control envelope, awaits CircuitReady, then runs a SECOND
  Aura handshake to the exit through a local loopback UDP proxy — the
  forwarder ferries datagrams between that proxy socket and the outer
  relay PacketConnection. The inner handshake therefore authenticates the
  EXIT cert (verified by the integration test asserting
  circuit.peer_id() == "localhost-exit"); the relay never sees the inner
  session keys.
- aura-cli::relay: rendezvous(conn, whitelist) -> Bridged{bridge} |
  Fallback{first_pkt} | Refused. 2-second window after handshake to receive
  ExtendBridge. Whitelist enforced; CircuitFailed on miss. Empty whitelist
  logs a warning and runs open. Timeout / non-control → Fallback so the
  same server can be both relay (for circuit clients) and exit (for direct
  clients) simultaneously.
- aura-cli::client: when [client.circuit] enabled → dial_circuit; falls
  back to normal aura_transport::dial when disabled.
- aura-cli::server: relay rendezvous wired before pool/CRL/router path.
  run_bridge spawns two forwarder tasks (conn↔bridge UDP socket).
- 3 integration tests: end-to-end (with peer_id assertion), whitelist
  rejection, back-compat (relay disabled → Err). 3 unit tests in relay.rs.

Workspace: 253 tests passed (247 baseline + 6 new), clippy -D warnings clean,
fmt clean. No new workspace deps. All 28 tracked tasks (v1 + v2 + v3.1) now
complete.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-27 13:16:07 +03:00

144 lines
6.9 KiB
TOML

# Aura VPN client configuration (project §9).
# Copy to client.toml and adjust. Paths may begin with `~` (expands to your home directory).
[client]
# Human-readable client name / id.
name = "laptop"
# Server UDP socket address.
server_addr = "203.0.113.10:443"
# Outer-TLS SNI (camouflage hostname) presented to the server. Also the name verified
# inside the Aura handshake against the server certificate's SAN.
sni = "cdn.example.com"
# Optional: drop privileges to this non-root user AFTER the TUN device has been brought up.
# Recommended when `aura client` is launched via sudo so the long-running router loop runs
# as an ordinary user. Linux uses setresuid/setresgid; macOS uses setgid/setuid; Windows is a
# no-op (use a service account instead). When omitted (or already running as non-root) no
# privilege change happens.
# run_as = "nobody"
# Suppress identifier fields (peer_id, client_ip, source_addr, ...) from log output. The events
# still fire; only the identifying fields are dropped before formatting. Default: false. Set to
# true to keep the local log file from accumulating per-session identifiers.
no_logs = false
# Optional fallback server addresses (IP or IP:port). When the primary `server_addr` cannot be
# reached on any transport, the client retries the bridges in a process-randomised order, using
# the same per-transport ports from [transport]. The bridge `:port` part is parsed but ignored.
# bridges = ["203.0.113.11", "203.0.113.12"]
[pki]
# Trust anchor (the Aura CA) and this client's leaf cert/key, all PEM.
# Issue with: aura pki issue-client --id laptop --out ~/.aura --ca ~/.aura
ca_cert = "~/.aura/ca.crt"
cert = "~/.aura/client.crt"
key = "~/.aura/client.key"
[tunnel]
# Requested TUN interface name (advisory on macOS, where the kernel assigns utunN).
tun_name = "aura0"
# Local address assigned to the TUN device, and its prefix length.
local_ip = "10.7.0.2"
prefix = 24
# TUN MTU.
mtu = 1420
# Tunnel resolver DNS (informational; the system resolver is used in v1).
dns = "10.7.0.1"
# Split-tunnel routing: the default action plus per-destination overrides.
[tunnel.split]
# Default for destinations matching no rule below: "VPN" or "DIRECT".
default = "VPN"
# Send these directly (bypass the tunnel): RFC1918 ranges stay on the LAN...
[[tunnel.split.direct]]
cidr = "192.168.0.0/16"
[[tunnel.split.direct]]
cidr = "10.0.0.0/8"
# ...and a corporate domain egresses directly (resolved to host routes at startup).
[[tunnel.split.direct]]
domain = "intranet.example.com"
# Force a more-specific range back through the VPN (longest-prefix wins over 10.0.0.0/8).
[[tunnel.split.vpn]]
cidr = "10.7.0.0/24"
# v2: OS-level split-tunnel routing. With `enabled = true` (the default) the client programs the
# system routing table at startup so DIRECT destinations bypass the TUN entirely — they continue
# to use the host's original default gateway, while only VPN-classified traffic reaches the
# tunnel. This eliminates the v1 user-space `send_direct` stub, where DIRECT packets were merely
# logged and dropped. The guard is RAII: the routes are rolled back when `aura client` exits.
#
# Linux: uses `ip route add ... via <gw> dev <egress>` for bypasses and `ip route add ... dev <tun>`
# for the VPN default; the VPN default carries metric 50 so it wins over DHCP-installed defaults.
# macOS: uses `route add -net <cidr> <gw>` for bypasses and `route add -net <cidr> -interface <tun>`
# for VPN routes.
# Windows: not implemented in v1 (the section is parsed but the install is a logged no-op).
[tunnel.os_routes]
# Master switch. `false` falls back to the v1 user-space router (the `send_direct` path drops
# DIRECT packets; kept intentionally as a fallback). Default: true.
enabled = true
# When `true`, every routing command is only logged (`would run: ...`) and not executed —
# useful for testing the plan without root. Default: false.
dry_run = false
# Optional explicit IPv4 default gateway. When omitted, auto-detected (Linux:
# `ip route show default`; macOS: `route -n get default`).
# gateway = "192.168.1.1"
# Optional explicit egress interface name (e.g. "eth0" on Linux, "en0" on macOS). When omitted,
# auto-detected alongside the gateway.
# egress_iface = "en0"
[mimicry]
# Enable traffic padding to blend packet sizes into HTTPS buckets.
padding = false
[transport]
# Fallback order tried left-to-right ("handover"): the first transport that connects wins. Aura's
# own UDP transport is primary; TCP/443 and QUIC (HTTP/3 mimicry) are fallbacks for networks that
# throttle or block plain UDP. Omitting this whole section uses ["udp","tcp","quic"] on 443/443/444.
order = ["udp", "tcp", "quic"]
# Per-transport server ports. The server IP comes from [client] server_addr above (its port there is
# ignored). The UDP transport and QUIC both ride UDP, so udp_port and quic_port MUST differ; TCP may
# reuse the UDP port number.
udp_port = 443
tcp_port = 443
quic_port = 444
# UDP: pad datagrams up to HTTPS size buckets to blur the on-wire size distribution.
obfuscate = true
# TCP: prepend a minimal HTTP/1.1 preamble (Host = [client] sni) so the open resembles plain HTTP.
masquerade = true
[transport.masks]
# Daily protocol-mask rotation. When `true`, every day at 05:00 MSK (= 02:00 UTC) the client
# derives a new (SNI, User-Agent, Server-header, padding-profile) tuple from
# HKDF-SHA256(CA-fingerprint, MSK-date) and uses it for any subsequent connect — the server derives
# the same tuple independently from the same CA fingerprint, so no wire coordination is needed.
# Existing connections keep the mask they connected with. Default: true.
# When `false`, the static values above ([client] sni, [transport] obfuscate, ...) are used as-is.
enabled = true
[transport.knock]
# UDP port-knocking. Must match the server's setting. Default: false.
enabled = false
knock_secret_source = "ca_fingerprint"
[transport.cover]
# Idle-time cover traffic. Must match the server's setting. Default: false.
enabled = false
mean_interval_ms = 500
jitter = 0.5
# v3.1 multi-hop / onion routing: dial through an entry-relay before reaching the exit-server.
# When `enabled = true`, the client opens an OUTER Aura UDP connection to `hops[0]` (the relay),
# sends one ExtendBridge envelope describing `hops[1]` (the exit), waits for CircuitReady, and
# then runs an INNER Aura handshake addressed to the exit through that relay — two AEAD layers
# per packet, the exit knows the client's CN but not the source IP, the relay knows the source
# IP but not the destination nor a single plaintext byte. Exactly two hops are required in
# v3.1; configure the relay-server with [server.relay] enabled = true and
# allow_extend_to = ["<this client's exit IP:port>"].
#
# Omitting the section (or `enabled = false`) keeps the v2 single-hop dial path intact —
# [client] server_addr / [transport] order rules apply as before.
# [client.circuit]
# enabled = true
# hops = ["198.51.100.5:443", "203.0.113.10:443"] # [entry_relay, exit_server] — literal IP:port