feat(gateway): TLS 1.3 only control plane and LNEx v3 channel-bound handshake

Replace the X25519/HKDF/ChaCha20 TCP layer with rustls TLS 1.3 (ALPN
vnox-lnex/3). Auto-generate a self-signed certificate keyed by the server
identity or load an operator certificate, publish the SPKI fingerprint,
bind HELLO and AUTH signatures to the TLS exporter, reject plaintext, TLS 1.2
and LNEx v2 peers with an explicit error. BREAKING: protocol v3.

Claude-Session: https://claude.ai/code/session_01GDjxLvBcnJqniFQGUGb1V4
This commit is contained in:
Loki 2026-10-24 22:05:30 +02:00
parent a5b9c324f7
commit 0d2af0ddd6
Signed by: boba
GPG key ID: 253067914055423B
45 changed files with 1322 additions and 806 deletions

View file

@ -12,6 +12,12 @@ admin_bind = "127.0.0.1:7601"
message_rate_per_sec = 5
# Burst size for the token bucket.
message_rate_burst = 10
# TLS 1.3 is always on (LNEx v3). With neither option below the gateway generates
# a self-signed certificate in <data_dir>/tls/ (key = server identity) and prints its
# SPKI SHA-256 fingerprint at startup. Clients pin it on first use.
# For a public CA certificate (for example Let's Encrypt) set both paths and restart on renewal:
# tls_cert_path = "/etc/letsencrypt/live/chat.example.org/fullchain.pem"
# tls_key_path = "/etc/letsencrypt/live/chat.example.org/privkey.pem"
[voice]
bind = "127.0.0.1:7700"