Restrict sops recipients to server and xps13 #16

Open
opened 2026-11-16 10:39:03 -05:00 by polen · 0 comments
Owner

Problem

.sops.yaml encrypts secrets/secrets.yaml for four recipients: xps13, pi, server, asus. Only the server consumes these secrets (agent API keys, deploy SSH key, Forgejo runner token, Monero view key). The pi has sops commented out, and asus uses none of them.

A compromise of the pi (SD card) or asus host key exposes every server secret.

Fix

  • Keep xps13 (editing) and server as recipients; remove pi and asus.
  • Run sops updatekeys secrets/secrets.yaml.
  • Rotate the secrets afterwards: the old recipients can still decrypt any earlier revision in git history.
## Problem `.sops.yaml` encrypts `secrets/secrets.yaml` for four recipients: `xps13`, `pi`, `server`, `asus`. Only the server consumes these secrets (agent API keys, deploy SSH key, Forgejo runner token, Monero view key). The pi has sops commented out, and asus uses none of them. A compromise of the pi (SD card) or asus host key exposes every server secret. ## Fix - Keep `xps13` (editing) and `server` as recipients; remove `pi` and `asus`. - Run `sops updatekeys secrets/secrets.yaml`. - Rotate the secrets afterwards: the old recipients can still decrypt any earlier revision in git history.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
polen/nixos#16
No description provided.