---
{
  "n": 65,
  "title": "Secret generation, storage and revocation",
  "abstract": "Generate a secret that grants access to a hosted server, and let the host revoke it.",
  "refs": [
    "message:11581"
  ],
  "seen": [
    "agent",
    "user",
    "system"
  ],
  "data": {
    "source": "user",
    "stage": "To do",
    "board": 12,
    "draft": false,
    "covers": [
      "2",
      "6"
    ],
    "agent": "board-filler",
    "dispatcher": "c35e7375-7ce3-4bc3-b1ae-7cdf73bd1488",
    "environment": "main",
    "dependencies": {
      "ticket:64": "confirmed"
    },
    "declined": []
  },
  "created": 1790395158.4610062,
  "updated": 1790395721.044679,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "ticket"
}
---
**What:** create a secret when hosting starts (or on demand), store it safely on the host, and let the hosting user revoke or rotate it.

**Why:** the secret is what a remote user proves they hold to be let in; it must be createable and cancelable.

**Touches:** secret generation, storage, host-side management command.

**Done when:** a hosting user can generate a secret and later revoke it so it stops working immediately.

**Risk:** a leaked or logged secret defeats the whole scheme; never print or store it in the clear where logs collect.