feat: secure Zara daemon with CURVE/ZAP and abuse controls #145

Merged

lost-rob0t merged 28 commits from rage/130-curve-zap-security into master

2026-08-22 18:41:06 +00:00

lost-rob0t commented

2026-08-22 14:11:43 +00:00

(Migrated from github.com)

Consumes #130 under the repository RAGE protocol.

Current state is intentionally red-first: research and evidence-derived design are committed, followed by deterministic security primitive tests before production implementation.

Planned scope:

CURVE client/server configuration and pinned server identity;
live ZAP key -> principal mapping with no payload-authoritative identity;
capability authorization boundary;
enrollment/rotation/revocation and owner-private key handling;
safe listener policy;
per-principal/session quotas and hostile-client isolation;
bounded structured redacted security audit;
focused security gate plus full repository/Nix exact-head gate.

RAGE start SHA: 2bf0adbca15ea8c161df7cf15c6c9cc4125317dc.

Do not merge while draft or while any exact-head gate is red/pending.

Consumes #130 under the repository RAGE protocol. Current state is intentionally **red-first**: research and evidence-derived design are committed, followed by deterministic security primitive tests before production implementation. Planned scope: - CURVE client/server configuration and pinned server identity; - live ZAP key -> principal mapping with no payload-authoritative identity; - capability authorization boundary; - enrollment/rotation/revocation and owner-private key handling; - safe listener policy; - per-principal/session quotas and hostile-client isolation; - bounded structured redacted security audit; - focused security gate plus full repository/Nix exact-head gate. RAGE start SHA: `2bf0adbca15ea8c161df7cf15c6c9cc4125317dc`. Do not merge while draft or while any exact-head gate is red/pending.