security #
secret handling, what the things i run expose to the network, what each credential can reach, and where a process's certificate trust comes from.
notes #
-
secrets — the sops store and its derived consumers, drift checks by digest, moving values without displaying them, rotation answers
-
exposure — checking from another host, binding, management planes, certificates for a private host, allowlists at a k3s ingress
-
credential-blast-radius — an orchestrator's admin credential, how workers copy it, one credential per workload, verifying holders
-
runtime trust stores — where python, grpc, rust, go, node, bun, zig and distro images get their roots, distrusting a root, and verifying from inside the process
-
systemd user sandboxing — enforcing filesystem namespaces, hiding credentials, and testing actual process access
related #
- dotenv-autoload — tools that load env files on their own
- tangled — workflow YAML environment values are public
- cloudflare-worker-rollback — a Worker rollback also reverts secret bindings
- tailscale — the private network these notes assume