Skip to content
gunkslab

Security

How the fleet is kept to the people meant to drive it, and where that falls short.

The short of it:

  • The brokers. The development broker in bench mode, and a broker whose certificates come from Vault, take nothing over the network but TLS and a certificate. The certificate’s name is the client’s login, and each login may use only its own topics.
  • The bots. A bot makes its own key, and its certificate is signed from a request it prints. Only the station ever commands a bot, and a bot stops by itself when it hears nothing.
  • Every change is checked for leaked secrets, known vulnerabilities and risky code before it merges. The broker’s configuration is tested on every change too.

Making and changing logins is a task, so it’s a guide: Logins and certificates.

  1. How it's securedThe design: logins as certificates, who may do what, checking the broker, revoking, the bots' keys, what's been tried for real
  2. What's protected, and every way inWhat's at stake, every way in and how it stands today, the checks on every change, the backlog, reporting a problem
  3. The bots' own networkWhy bots belong on a network of their own, and how to set one up
  4. Checking it on a real botWhat hasn't been run on a bot yet, and the checks to run when one is on the bench
  5. Known limitsWhat the design doesn't cover, or doesn't yet, and where each is tracked