Skip to content

fix(secrets): odin's ingest token, which the soc stack requires, is in git - #1046

Merged
Gerrrt merged 1 commit into
mainfrom
gerrrt/soc-ingest-token-sops
Oct 7, 2026
Merged

Gerrrt merged 1 commit into
mainfrom
gerrrt/soc-ingest-token-sops

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Oct 7, 2026

Copy link
Copy Markdown
Owner

What

This commits odin's secrets/soc.sops.yaml as it stands on odin. It adds one key, INGEST_TOKEN: the token odin's Alloy sends to alexander's ingest proxy. Its lab-side copy is INGEST_TOKEN_ODIN in secrets/lab.sops.yaml.

Why

Checks

  • Byte for byte the same as odin's: sha256 068c37943918e9199f30d5292f39b01feba9a7ab24615079cc71b04fb13ba0fb on both.
  • The diff is the new encrypted key plus sops's own lastmodified and mac. Every other value is unchanged, and the recipient is the same single age key.
  • It decrypts on odin with a valid MAC. It was decrypted to /dev/null; no value was printed.
  • The token is the one in use. Over the last 10 minutes alexander's ingest proxy rejected nothing from 10.0.30.60.
  • check-sops-encrypted.sh and check_sops_rules.py pass.

After merge

odin's working copy will be identical to main, so the next git pull there leaves nothing to stash.

🤖 Generated with Claude Code

…n git

stacks/soc/compose.yaml requires INGEST_TOKEN (${INGEST_TOKEN:?}), but
secrets/soc.sops.yaml on main never had it: the key was added on odin
on 2026-10-04 at 13:09 UTC, during #834's per-client ingest tokens, and
stayed an uncommitted edit there. odin ran on that copy; a fresh
checkout would fail make up.

This is odin's file byte for byte (sha256 068c3794...). It adds one key;
every other value is unchanged, and the recipient is the same one age
key. It decrypts on odin with a valid MAC, and alexander's ingest proxy
has rejected nothing from odin.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings October 7, 2026 17:23
@Gerrrt
Gerrrt enabled auto-merge (squash) October 7, 2026 17:25

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.

🔵 Needs a closer look

The encrypted token’s value and correspondence with the proxy token cannot be independently verified from the diff.

0 open findings

What changed in this PR

Adds Odin’s encrypted ingest token required by the SOC stack.

Changes:

  • Adds INGEST_TOKEN.
  • Updates SOPS metadata and MAC.
File Description
secrets/​soc.sops.yaml Stores Odin’s encrypted lab ingest token.

🧠 Review effort: Balanced


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

@Gerrrt

Gerrrt commented Oct 7, 2026

Copy link
Copy Markdown
Owner Author

On the review's point that the diff can't show this token matches the proxy's, I checked it without printing either value. Each side's decrypted value was hashed with sha256; the first 16 hex digits:

  • odin, INGEST_TOKEN in this file: 404534e5e2cebb01
  • alexander, INGEST_TOKEN_ODIN in secrets/lab.sops.yaml: 404534e5e2cebb01

They are the same token. No code change needed.

🤖 Addressed by Claude Code

@Gerrrt
Gerrrt merged commit 0092208 into main Oct 7, 2026
9 checks passed
@Gerrrt
Gerrrt deleted the gerrrt/soc-ingest-token-sops branch October 7, 2026 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants