docs: TLS 1.3 trust model, LNEx v3 and operator guide

This commit is contained in:
Loki 2026-10-24 22:05:30 +02:00
parent ff051b7480
commit 58662de2e9
12 changed files with 348 additions and 125 deletions

View file

@ -76,10 +76,11 @@ max_pps_per_user = 60
# Generated automatically on first start if not present.
keypair_path = "/var/lib/vnox/node.key"
# TLS certificate for the TCP gateway.
# If not set, a self-signed certificate is generated.
# tls_cert = "/etc/vnox/tls/cert.pem"
# tls_key = "/etc/vnox/tls/key.pem"
# TLS 1.3 is always on (LNEx v3). TLS keys live in the [gateway] section:
# tls_cert_path = "/etc/letsencrypt/live/chat.example.org/fullchain.pem"
# tls_key_path = "/etc/letsencrypt/live/chat.example.org/privkey.pem"
# Both unset: a self-signed certificate is generated in <data_dir>/tls/ and its
# fingerprint is logged. See docs/02-protocol/tls.md.
# ─── CHANNELS ──────────────────────────────────────────────────────────────

View file

@ -214,5 +214,5 @@ with a migration guide.
- [ ] `node.key` backup exists and is stored securely
- [ ] `VNOX_LOGGING_LEVEL` is `info` or `warn` in production (not `trace`)
- [ ] `[gateway.rate_limits]` are configured appropriately for your user base
- [ ] TLS certificate is valid (or TOFU is acceptable for your use case)
- [ ] TLS: either a CA certificate (`tls_cert_path`/`tls_key_path`) or the self-signed fingerprint (`data_dir/tls/fingerprint.txt`) is published to users; no TLS-terminating proxy in front of TCP 7600
- [ ] Federation disabled if not needed (`[federation] enabled = false`)