[BUG] Exact native rename rejects valid non-UTF-8 destination components #31

Open
opened 2026-10-12 14:27:57 +02:00 by erikinkinen · 0 comments
Owner

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

  • Component repository/revision and Integration source graph: original vfsd source, original Integration graph.
  • Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report.
  • Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred.
  • Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced.
  • Last known working revision, if known: not established.

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.

## 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 - Component repository/revision and Integration source graph: [original vfsd source](https://git.erikinkinen.fi/erix/vfsd/commit/8c42847b175abd4260f69ffc67cbf23d41aa94a7), [original Integration graph](https://git.erikinkinen.fi/erix/integration/commit/a615de2f69c25d4575d0c349757a0017082f988b). - Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report. - Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred. - Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced. - Last known working revision, if known: not established. ## 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](https://git.erikinkinen.fi/erix/integration/issues/65) tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:19 +01:00
Sign in to join this conversation.
No milestone
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
erix/vfsd#31
No description provided.