Add alternatives for compatibility wrappers#1842
Merged
Merged
Conversation
4 tasks
oferchen
added a commit
that referenced
this pull request
Apr 29, 2026
Static analysis of every entry point that consumes or emits a path on Windows: CLI parsing, flist encode/decode, daemon sanitization, local- copy planning, and symlink safety. Compares against upstream rsync 3.4.1 (Cygwin build) and identifies one high-severity correctness bug (F1: backslash leaks into wire-encoded filenames) plus four lower- severity gaps. Audit-only commit; F1 fix is filed as a follow-up because it requires a wire-format change with dedicated golden tests.
oferchen
added a commit
that referenced
this pull request
May 1, 2026
Static analysis of every entry point that consumes or emits a path on Windows: CLI parsing, flist encode/decode, daemon sanitization, local- copy planning, and symlink safety. Compares against upstream rsync 3.4.1 (Cygwin build) and identifies one high-severity correctness bug (F1: backslash leaks into wire-encoded filenames) plus four lower- severity gaps. Audit-only commit; F1 fix is filed as a follow-up because it requires a wire-format change with dedicated golden tests.
1 task
oferchen
added a commit
that referenced
this pull request
May 1, 2026
…#3515) Document the High-severity backslash-leak finding with reproduction steps and the remediation plan referencing task #1905. Refines the parent audit #1842 (windows-path-normalization.md) with a focused finding-level write-up: code paths, reproduction commands (daemon and batch capture), upstream comparison via Cygwin, the path_bytes_to_wire helper plan, regression-test obligations, and the Windows-sender -> Linux-receiver CI matrix entry.
oferchen
added a commit
that referenced
this pull request
May 5, 2026
Static analysis of every entry point that consumes or emits a path on Windows: CLI parsing, flist encode/decode, daemon sanitization, local- copy planning, and symlink safety. Compares against upstream rsync 3.4.1 (Cygwin build) and identifies one high-severity correctness bug (F1: backslash leaks into wire-encoded filenames) plus four lower- severity gaps. Audit-only commit; F1 fix is filed as a follow-up because it requires a wire-format change with dedicated golden tests.
oferchen
added a commit
that referenced
this pull request
May 5, 2026
…#3515) Document the High-severity backslash-leak finding with reproduction steps and the remediation plan referencing task #1905. Refines the parent audit #1842 (windows-path-normalization.md) with a focused finding-level write-up: code paths, reproduction commands (daemon and batch capture), upstream comparison via Cygwin, the path_bytes_to_wire helper plan, regression-test obligations, and the Windows-sender -> Linux-receiver CI matrix entry.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Testing
https://chatgpt.com/codex/tasks/task_e_69056b36da6483238a653b2f57b32db5