[BUG] Exact native rename rejects valid non-UTF-8 destination components #31
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/vfsd#31
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
Exact native rename rejects valid non-UTF-8 destination components. Maintained validation cannot reach its intended successful boundary.
Reproduction
Run the existing two long raw-name mutation controls against their original retained provider candidate. Supply a destination component that fits the V2 wire and counted storage but contains non-UTF-8 bytes. The original failing source and current repairs are distinct; failures and true exit statuses are retained.
Expected and actual behavior
A native raw component within the complete request/storage bounds should preserve its exact bytes without changing original source or route selection. mutate_exact_entry applies the administrative lib_fs_name::validate_name rule and rejects the native raw destination solely because it is not UTF-8, before the original retained-provider mutation can run.
Environment and identity
Evidence and prior checks
Use the shared native creation-component validator; preserve empty, dot, dot-dot, slash and NUL refusals, full byte budgets, original candidate identity and authority. Existing independent raw-name controls remain. Full source validation and signed publication continue in parallel.
Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired.
Tracking
Phase completion tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.