Unicode: a file and a folder whose names differ only in NFC/NFD form can still be created side by side #979

Closed
opened 2026-10-20 06:00:23 +00:00 by Cordy · 0 comments
Owner

Found in the batch 4 review of #963/#976 (review-f finding 2, 2026-10-19), with a probe on s3.

Since v0.6.351 a file and a folder can no longer share a name. Names that differ only in Unicode normalization still slip through:

  • a file written onto a folder stored in the other form;
  • a write below a file stored in the other form;
  • a file renamed onto such a folder.

Mkdir is already protected (#934).

Expected: every collision check resolves the existing entry in either Unicode form (composed spelling first, as #934 does for path segments) and refuses with the same storage error as an exact-name collision.

To do: test each case above on posix and s3, through REST, WebDAV and TUS.

Found in the batch 4 review of #963/#976 (review-f finding 2, 2026-10-19), with a probe on s3. Since v0.6.351 a file and a folder can no longer share a name. Names that differ only in Unicode normalization still slip through: - a file written onto a folder stored in the other form; - a write below a file stored in the other form; - a file renamed onto such a folder. Mkdir is already protected (#934). **Expected:** every collision check resolves the existing entry in either Unicode form (composed spelling first, as #934 does for path segments) and refuses with the same storage error as an exact-name collision. **To do:** test each case above on posix and s3, through REST, WebDAV and TUS.
Cordy closed this issue 2026-10-27 03:15:04 +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#979
No description provided.