#411 dogfood fix: drain fallback for principal-less paths #413
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "kd-fallback"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
First real drain on cairn-enc failed on three pre-per-user-homes relics at the backend root: per-user custody has no principal to resolve for them ("encrypt: no authenticated user in context").
Drainer.Fallback, built from the active recovery/deployment identities). Today they open only via the retiring recovery key, so this preserves exactly their current access — on the new key. Space and home paths keep the normal custody-re-resolution route./homeno longer resolves its own name as a username — per-user custody is never asked to mint keys for a bogus principal (edge exposed by the/home/Mülltrennung.docxghost).userForPathcases.