Skip to content

feat(sensor): fenrir's own age key and its ingest token (#834) - #905

Merged
Gerrrt merged 1 commit into
mainfrom
gerrrt/fenrir-sensor-secrets
Oct 4, 2026
Merged

Gerrrt merged 1 commit into
mainfrom
gerrrt/fenrir-sensor-secrets

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Oct 4, 2026

Copy link
Copy Markdown
Owner

What this is

Step 3 of the lab ingest-proxy rollout (#834, stacks/lab/README.md), run on fenrir:

  • make secrets-init STACK=sensor replaced the sensor rule's REPLACE_WITH_SENSOR_AGE_PUBLIC_KEY placeholder with fenrir's public key, age1er585qkxfqyyjf4zqpaukzlngs06r64gx2ndlnmj24pxw0g22amq40u555.
  • make secrets-edit STACK=sensor created secrets/sensor.sops.yaml, holding INGEST_TOKEN (fenrir's token for alexander's proxy) encrypted to that key.

Both files are public key and ciphertext only.

How it got here

fenrir committed it as bf659d8, but fenrir has no GitHub credentials and shouldn't: it's on VLAN 30. So the commit came over as a git format-patch paste and was rebuilt here. The terminal had hard-wrapped the paste at 72 columns, so the lines were rejoined by width. Both rebuilt files hash to the patch's own index lines, aa35e1b (.sops.yaml) and bcc9d6f (secrets/sensor.sops.yaml), so they're byte-identical to fenrir's.

Verified

  • check_sops_rules.py passes: secrets/sensor.sops.yaml is encrypted to exactly the key its rule lists. One recipient is allowed for the sensor stack, whose token a rebuild regenerates.
  • check_docs.py and yamllint pass.

After merge

On fenrir, git fetch origin, then git diff HEAD origin/main -- .sops.yaml secrets/sensor.sops.yaml must print nothing. Then git switch main && git reset --hard origin/main returns its checkout to a clean main. GitHub's squash merge gives the commit a new ID, so without this, fenrir's main would diverge from GitHub's.

🤖 Generated with Claude Code

Step 3 of the lab ingest-proxy rollout (stacks/lab/README.md). make
secrets-init STACK=sensor on fenrir wrote fenrir's public key into the sensor
rule in place of its placeholder. make secrets-edit STACK=sensor encrypted
INGEST_TOKEN, fenrir's token for alexander's proxy, to that key alone.

Committed on fenrir as bf659d8, which has no push credentials and should not
have any: it sits on VLAN 30. Carried here as a patch and rebuilt
byte-for-byte; both blobs match the patch's index lines (aa35e1b, bcc9d6f).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Gerrrt Gerrrt added the security A credential, an exposure, or a control that is weaker than recorded label Oct 4, 2026
Copilot AI balanced review requested due to automatic review settings October 4, 2026 13:42
@Gerrrt Gerrrt added the lab stacks/lab on alexander (VLAN 30) label Oct 4, 2026
@Gerrrt
Gerrrt enabled auto-merge (squash) October 4, 2026 13:42

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🔵 Needs a closer look

Host-side decryption and token agreement with the ingest proxy still require verification.

Review effort: Balanced
Findings: None

What changed in this PR

Provisions fenrir’s sensor credentials for the authenticated lab ingest rollout in #834.

Changes:

  • Replaces the sensor recipient placeholder with fenrir’s public age key.
  • Adds the ingest token encrypted to that key.
File Description
secrets/​sensor.sops.yaml Stores fenrir’s encrypted ingest token.
.sops.yaml Configures fenrir’s key as the sensor recipient.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@Gerrrt
Gerrrt merged commit bf6e402 into main Oct 4, 2026
9 checks passed
@Gerrrt
Gerrrt deleted the gerrrt/fenrir-sensor-secrets branch October 4, 2026 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lab stacks/lab on alexander (VLAN 30) security A credential, an exposure, or a control that is weaker than recorded

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants