From f9d2dfca2126b1cde7663e792a0338406bfd2d9e Mon Sep 17 00:00:00 2001 From: Ari Sosnovsky Date: Fri, 16 Oct 2026 07:03:27 -0400 Subject: [PATCH] plan: DEC-12 decided (in-process rustls TLS) Co-Authored-By: Claude Sonnet 5.5 --- plan/decisions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/plan/decisions.md b/plan/decisions.md index 037d98f..08a790b 100644 --- a/plan/decisions.md +++ b/plan/decisions.md @@ -142,8 +142,8 @@ Tokens are minted with `slinuxm token create `, printed once, and never st ## DEC-12 — TLS terminated in-process with rustls -**Status:** Proposed +**Status:** Decided 2026-10-16 Bearer tokens over plain HTTP are readable on the wire, and LAN exposure is the intended deployment. The service gets native TLS: `server.tls.enabled`, `cert_file`, `key_file`, with certificate reload on SIGHUP so ACME or sops-managed rotation needs no restart. A reverse proxy still works and nothing depends on it. rustls is already in the dependency tree and openssl stays out. When TLS is enabled the MCP Origin allowlist uses `https://`. TLS is optional and off by default; with it off nothing changes. A non-loopback bind without TLS logs a startup warning but is not refused. -**Decision:** +**Decision:** Accepted by the user: option A, in-process rustls. TLS stays optional and off by default.