[BUG] Native EXT mutations impose an unintended UTF-8 basename restriction #21
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/e2fsd#21
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Summary
Native ext mutations reject valid non-UTF-8 basenames before reaching the authorized operation.
Reproduction
At the original source, supply a 255-byte basename containing
0xffthrough a held parent on writable media. Creation, link, rename, removal and recovery paths can reach a text-only name validator.Expected and actual behavior
Native basenames must preserve bytes within the ext name limit. Reject empty names, NUL, separators and navigation aliases without imposing UTF-8. Keep configured casefold/encryption behavior, administrative path rules and the original authority boundaries.
Environment and identity
Evidence and prior checks
The raw native component rule and physical name bound must apply consistently across the shared mutation paths.
Tracking
Fixes and full-name regression coverage are included in #44.