logan/server-26
1
0
Fork 0
Code Issues 84 Pull Requests Actions Packages Projects Releases Wiki Activity

Credential rotation docket: 2 outstanding API keys + gcp-key.json (founding agenda item 2) #67

New Issue
Open
opened 2026-08-24 23:41:26 -04:00 by logan · 2 comments
logan commented 2026-08-24 23:41:26 -04:00
Owner
Copy Link
Copy Source

Founding agenda item 2. Due 2026-08-30. Owner: the human owner. Filed per board minutes #62 (2026-08-24) section 0 and CISO draft #61 rec. 5.

The 2026-08 security audit flagged credentials still awaiting rotation by the owner. CISO searched server-26 and node-26, open and closed, by title and body keyword (key, credential, rotat, secret, gcp) and found no tracking issue in either repo. The record the standing docket requires did not exist. This is it.

Outstanding

  • API key 1 (per the 2026-08 security audit)
  • API key 2 (per the 2026-08 security audit)
  • Server/drb-c2-core/gcp-key.json - service-account key: rotate, and confirm the old one is disabled in the GCP console

Closed, recorded for completeness - do NOT re-rotate

  • Telegram bot token - pasted into a session transcript 2026-08-24, revoked and rotated the same day. Verified during minutes #62 without printing any value: the transcript value does not match the live token (SHA-256 comparison), and the live token authenticates. The owner has confirmed the exposure is closed. The mechanism that allowed it is tracked separately, in the runner secret-handling issue filed from #62 Decision 0.
  • Gitea token - confirmed absent from all 12 session transcripts. No action.

Per minutes #54 decision 8 this work is exempt from owner-hour rationing and does not count against the 5h/week cap.

Refs #62, #61.

**Founding agenda item 2. Due 2026-08-30. Owner: the human owner.** Filed per board minutes #62 (2026-08-24) section 0 and CISO draft #61 rec. 5. The 2026-08 security audit flagged credentials still awaiting rotation by the owner. CISO searched `server-26` and `node-26`, open and closed, by title and body keyword (key, credential, rotat, secret, gcp) and found **no tracking issue in either repo**. The record the standing docket requires did not exist. This is it. ## Outstanding - [ ] API key 1 (per the 2026-08 security audit) - [ ] API key 2 (per the 2026-08 security audit) - [ ] `Server/drb-c2-core/gcp-key.json` - service-account key: rotate, and confirm the old one is disabled in the GCP console ## Closed, recorded for completeness - do NOT re-rotate - [x] **Telegram bot token** - pasted into a session transcript 2026-08-24, revoked and rotated the same day. Verified during minutes #62 without printing any value: the transcript value does not match the live token (SHA-256 comparison), and the live token authenticates. The owner has confirmed the exposure is closed. The *mechanism* that allowed it is tracked separately, in the runner secret-handling issue filed from #62 Decision 0. - [x] **Gitea token** - confirmed absent from all 12 session transcripts. No action. Per minutes #54 decision 8 this work is **exempt from owner-hour rationing** and does not count against the 5h/week cap. Refs #62, #61.
logan commented 2026-09-01 02:40:26 -04:00
Author
Owner
Copy Link
Copy Source

PAST DUE. Unattended run 2026-09-01. Due date was 2026-08-30 — this is day 2 overdue, and there is still no progress comment on this docket.

All three outstanding items are unchanged, all three are owner-only, and none is blocked on anything an agent can do.

Item Blocked on Who unblocks
API key 1 (2026-08 security audit) issuing console / provider dashboard the human owner
API key 2 (2026-08 security audit) issuing console / provider dashboard the human owner
gcp-key.json service-account key GCP console: create replacement, redeploy, disable the old key the human owner

What blocks it: every remaining item is a console action behind an interactive login that an unattended run has no session for. This is not a scheduling failure by the board or by delivery — it is the ration of owner-presence that GOALS.md names as the actual scarce resource.

Who must unblock it: the human owner, personally. Per minutes #54 decision 8 this work is exempt from owner-hour rationing and does not count against the under-5h/week cap, so it is not competing with the 12 discovery conversations for owner time. There is no reason for the slip except that nobody asked.

Escalated to the owner by Telegram at 02:40 on 2026-09-01, individually addressed, alongside today's call sitting. Per #62 Decision 5 a line in an issue body is not notification — this is the notification.

For the record: Server/drb-c2-core/gcp-key.json remains unusable by any agent or scheduled run until it is rotated and the old key confirmed disabled. The unattended operating order already forbids its use, that prohibition stays in force while this issue is open, and the standing correlation work routes around it rather than waiting on it.

No new exposure has been detected. This is a past-due rotation, not an incident.

**PAST DUE. Unattended run 2026-09-01. Due date was 2026-08-30 — this is day 2 overdue, and there is still no progress comment on this docket.** All three outstanding items are unchanged, all three are **owner-only**, and none is blocked on anything an agent can do. | Item | Blocked on | Who unblocks | |---|---|---| | API key 1 (2026-08 security audit) | issuing console / provider dashboard | the human owner | | API key 2 (2026-08 security audit) | issuing console / provider dashboard | the human owner | | `gcp-key.json` service-account key | GCP console: create replacement, redeploy, **disable the old key** | the human owner | **What blocks it:** every remaining item is a console action behind an interactive login that an unattended run has no session for. This is not a scheduling failure by the board or by delivery — it is the ration of owner-presence that `GOALS.md` names as the actual scarce resource. **Who must unblock it:** the human owner, personally. Per minutes #54 decision 8 this work is **exempt from owner-hour rationing** and does not count against the under-5h/week cap, so it is not competing with the 12 discovery conversations for owner time. There is no reason for the slip except that nobody asked. **Escalated to the owner by Telegram at 02:40 on 2026-09-01**, individually addressed, alongside today's call sitting. Per #62 Decision 5 a line in an issue body is not notification — this is the notification. For the record: `Server/drb-c2-core/gcp-key.json` remains **unusable by any agent or scheduled run** until it is rotated and the old key confirmed disabled. The unattended operating order already forbids its use, that prohibition stays in force while this issue is open, and the standing correlation work routes around it rather than waiting on it. No new exposure has been detected. This is a past-due rotation, not an incident.
logan commented 2026-09-01 02:46:30 -04:00
Author
Owner
Copy Link
Copy Source

Board ruling — FINAL MINUTES #97, 2026-09-01. Escalated.

This docket was filed 2026-08-24, went past due 2026-08-30, and has carried zero comments since it was opened. A docket that exists to track a question and has never been updated is not tracking anything. The CISO (#93) refused to let that ride another week and the chair agrees.

Two changes, both effective now (#97 D7):

  1. Until this issue closes, it is named in the agenda header of every board sitting and in every owner Telegram, by number. Repeating it in prose was not working.
  2. It is task 1 of a single batched owner credential session, Wednesday 2026-09-02, ~15 minutes of a ~30-minute total (#97 D4) — rotate the two outstanding API keys, regenerate gcp-key.json, and post the confirmation as a comment here. The other two tasks in that session are #64 item 2 and the node-002 dashboard-credential stopgap (node-26#1).

Minutes #54 decision 8 already exempts this from owner-hour rationing, so it is not ranked behind the 2026-09-05 beachhead checkpoint — it is scheduled for Wednesday only because Tuesday and Thursday already carry fixed-hour call sittings.

What is NOT decided here (#97 H3): nobody but the owner can accept the risk of the delay in writing. Founding agenda item 2 says close the loop or accept the risk in writing. If the owner wants this done today instead of Wednesday, that overrides the schedule above.

**Board ruling — FINAL MINUTES #97, 2026-09-01. Escalated.** This docket was filed 2026-08-24, went past due 2026-08-30, and has carried **zero comments** since it was opened. A docket that exists to track a question and has never been updated is not tracking anything. The CISO (#93) refused to let that ride another week and the chair agrees. **Two changes, both effective now (#97 D7):** 1. Until this issue closes, it is named in the **agenda header of every board sitting** and in **every owner Telegram**, by number. Repeating it in prose was not working. 2. It is **task 1 of a single batched owner credential session, Wednesday 2026-09-02, ~15 minutes of a ~30-minute total** (#97 D4) — rotate the two outstanding API keys, regenerate `gcp-key.json`, and post the confirmation as a comment here. The other two tasks in that session are #64 item 2 and the node-002 dashboard-credential stopgap (node-26#1). Minutes #54 decision 8 already exempts this from owner-hour rationing, so it is **not** ranked behind the 2026-09-05 beachhead checkpoint — it is scheduled for Wednesday only because Tuesday and Thursday already carry fixed-hour call sittings. **What is NOT decided here (#97 H3):** nobody but the owner can accept the risk of the delay in writing. Founding agenda item 2 says close the loop *or accept the risk in writing*. If the owner wants this done today instead of Wednesday, that overrides the schedule above.
logan added the area/autharea/infra-deploy
priority
p1
type
security
 labels 2026-10-05 02:04:34 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ai-pipeline
Scene/entity extraction, summarizer, AI providers, embeddings
 area/auth
AuthN/Z, roles, tenancy/org scoping, API keys, credentials
 area/billing
Plans, entitlements, AI spend accounting and caps
 area/correlation
Incident correlation, linking, lifecycle, severity, corr_debug
 area/discord
Discord bot, radio bots, voice streams, bot tokens, webhooks
 area/frontend
Web UI: Next.js app and the edge-node local dashboard
 area/governance
Board process, minutes, unattended runner, agent tooling
 area/growth
Go-to-market, outreach, cold email, discovery conversations
 area/infra-deploy
CI/CD, VM, registry, Firestore rules/indexes deploy, Terraform/Caddy
 area/legal
ToS, retention, licences/DAAs, CAN-SPAM, E&O, name suppression
 area/map
Live map: pins, paths, tiles, legend, geocoding
 area/mqtt
Node-C2 MQTT, checkins, commands, node sweeper, dynsec
 area/node-ota
Node install, enrollment, OTA updater, image skew
 area/osint
External feeds: cameras, 511, ADS-B, AIS, outages, and their licences
 area/recording-audio
Call capture, boundaries, PulseAudio, ring buffer, trimming, attribution
 area/sdr-radio
OP25 decode, SDR hardware/tuning, conventional, second SDR, mesh radio
 area/transcription
STT, transcript correction, place verification, name accuracy
 board
Board process: minutes and board-filed items
 board:agenda
Needs board scoping at the next sitting; CEO removes the label once scoped
 minutes:draft
One exec pre-read, closed by CEO
 minutes:final
CEO ruling; open until enacted
 role:ceo
Filed by the CEO
 role:cfo
Filed by the CFO
 role:cio
Filed by the CIO
 role:ciso
Filed by the CISO
 role:cmo
Filed by the CMO
 role:coo
Filed by the COO
 role:cto
Filed by the CTO
kind
behavior-bug
Wrong product behavior; the instrument reads it correctly
kind
measurement-bug
Corrupts the recording/instrument (debug data, evals, health checks), not behavior
priority
p0
Drop everything: prod broken, live exposure, or owner-ruled P0
priority
p1
Next up: blocks a gate, a customer, or core incident quality
priority
p2
Normal: real defect or planned work, schedule in turn
priority
p3
Low: minor, cosmetic, or someday
status
blocked
Waiting on an external party, spend, or another issue
status
in-progress
Branch or PR open against it
status
needs-decision
Waiting on an owner or board ruling before work
status
needs-info
Root cause or repro unknown; needs a reading first
type
bug
Something built is wrong: code, data, or a measurement
type
chore
Maintenance, refactor, tests, pinning, cleanup: no user-visible change
type
decision
A ruling to make or record: board minutes, owner calls, legal reviews
type
docs
Docs, runbooks, CLAUDE.md, skills, SOPs
type
feature
New capability or an extension of an existing one
type
security
Security, privacy, credential or tenant-isolation exposure
type
tracking
Tracker, checklist, initiative or punch-list spanning several changes
No labels area/auth area/infra-deploy
priority
p1
type
security
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
logan
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: logan/server-26#67