Remote crypto role (storage.encryption.remoteUrl) follows the cluster's key decision with several instances #1187

Open
opened 2026-11-19 21:01:33 +00:00 by Cordy · 0 comments
Owner

Follow-up from #742 batch B part 1 (v0.6.411, spec-742b1.md S5.5; decision R5-Q3).

Today (v0.6.411)

  • With several instances (coordination on) and encryption enabled, storage.encryption.remoteUrl is refused at start.
  • The ERROR line points at multi-instance#requirements, and the process exits 1.
  • Reason: the remote crypto role (#33) seals with its own configured identities. It cannot follow the cluster's decided keys (#1178), and the key records cannot see it. A member that used it could seal file content to keys the cluster has not decided.

What it would take

  • The crypto role learns the cluster's decision. It would be a member of the coordination store, or receive the decided recipients per request, authenticated.
  • It publishes its fingerprints in the key records like a member, so the decision and the start guard include it.
  • Re-encryption and the drain gate (409 keys-not-decided) cover it.

Until then, scaling the age/argon2 work apart from the members is a single-instance option only.

Follow-up from #742 batch B part 1 (v0.6.411, spec-742b1.md S5.5; decision R5-Q3). **Today (v0.6.411)** - With several instances (coordination on) and encryption enabled, `storage.encryption.remoteUrl` is refused at start. - The ERROR line points at `multi-instance#requirements`, and the process exits 1. - Reason: the remote crypto role (#33) seals with its own configured identities. It cannot follow the cluster's decided keys (#1178), and the key records cannot see it. A member that used it could seal file content to keys the cluster has not decided. **What it would take** - The crypto role learns the cluster's decision. It would be a member of the coordination store, or receive the decided recipients per request, authenticated. - It publishes its fingerprints in the key records like a member, so the decision and the start guard include it. - Re-encryption and the drain gate (409 `keys-not-decided`) cover it. Until then, scaling the age/argon2 work apart from the members is a single-instance option only.
Sign in to join this conversation.
No labels
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: Cordy/Cairn#1187
No description provided.