Give and transfers under keycloak-profile custody: the receiving account cannot open the earlier files (#1054 follow-up) #1078

Open
opened 2026-11-02 19:05:27 +00:00 by Cordy · 0 comments
Owner

Problem. Under keycloak-profile custody each account's age key lives with its Keycloak account. When a Keycloak account is deleted and created again, the earlier files stay encrypted to the earlier key. After Give to the current {name} (v0.6.387, #1054) or an owner transfer, the receiving account sees the names but cannot open the contents. Recovery custody can still open them. Existing transfers have the same limit. It is documented in encryption.md and users-access.md (decision U2 of #1054).

Proposal to research. During Give and transfers, re-encrypt the moved files' owner records to the receiving account, using the recovery identity where it is configured, and say clearly when it is not.

Next step. Research by the playbook: how others handle key hand-over at offboarding (Nextcloud server-side encryption with the recovery key, Tresorit, Boxcryptor, Proton Drive), and what went wrong for them. Then decide, mock up and build.

Refs: #1054 spec U2 and section 15.3, #1058 residual 6.

**Problem.** Under `keycloak-profile` custody each account's age key lives with its Keycloak account. When a Keycloak account is deleted and created again, the earlier files stay encrypted to the earlier key. After **Give to the current {name}** (v0.6.387, #1054) or an owner transfer, the receiving account sees the names but cannot open the contents. Recovery custody can still open them. Existing transfers have the same limit. It is documented in encryption.md and users-access.md (decision U2 of #1054). **Proposal to research.** During Give and transfers, re-encrypt the moved files' owner records to the receiving account, using the recovery identity where it is configured, and say clearly when it is not. **Next step.** Research by the playbook: how others handle key hand-over at offboarding (Nextcloud server-side encryption with the recovery key, Tresorit, Boxcryptor, Proton Drive), and what went wrong for them. Then decide, mock up and build. Refs: #1054 spec U2 and section 15.3, #1058 residual 6.
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#1078
No description provided.