Deleted files: entries whose metadata cannot be decrypted vanish silently; a deleted space's files cannot be previewed from the trash without the recovery key #968

Closed
opened 2026-10-19 00:20:25 +00:00 by Cordy · 0 comments
Owner

Found in batch 3 (Task D, 2026-10-19). Pre-existing. Two related trash problems.

  1. Entries vanish silently. An entry in Deleted files whose sidecar or metadata cannot be decrypted (wrong key scope, missing key) is dropped from the listing with no WARN. Admins cannot tell that something in the trash has become unreadable. Expected: the entry is listed with a clear "cannot be read" state (name and date where known), and a rate-limited WARN names the entry, the holder and the cause.
  2. No preview inside a deleted space. A whole deleted space sits in the deleter's personal trash, but its files are encrypted to the space's group key. Previewing or downloading a file inside that entry fails unless the instance has a recovery identity. Restoring the space works. Expected: preview and download resolve the key scope recorded with the entry (the space id or key name from #935 and the batch-3 KeyName), or the UI says that the space must be restored first.

Test both with both custodies, on posix and s3.

Found in batch 3 (Task D, 2026-10-19). Pre-existing. Two related trash problems. 1. **Entries vanish silently.** An entry in Deleted files whose sidecar or metadata cannot be decrypted (wrong key scope, missing key) is dropped from the listing with no WARN. Admins cannot tell that something in the trash has become unreadable. Expected: the entry is listed with a clear "cannot be read" state (name and date where known), and a rate-limited WARN names the entry, the holder and the cause. 2. **No preview inside a deleted space.** A whole deleted space sits in the deleter's personal trash, but its files are encrypted to the space's group key. Previewing or downloading a file inside that entry fails unless the instance has a recovery identity. Restoring the space works. Expected: preview and download resolve the key scope recorded with the entry (the space id or key name from #935 and the batch-3 KeyName), or the UI says that the space must be restored first. Test both with both custodies, on posix and s3.
Cordy closed this issue 2026-10-27 03:15:07 +00:00
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#968
No description provided.