Skip to content

Add alternatives for compatibility wrappers#1842

Merged
oferchen merged 2 commits into
masterfrom
enable-side-by-side-installation-of-rsync
Nov 1, 2025
Merged

Add alternatives for compatibility wrappers#1842
oferchen merged 2 commits into
masterfrom
enable-side-by-side-installation-of-rsync

Conversation

@oferchen
Copy link
Copy Markdown
Owner

@oferchen oferchen commented Nov 1, 2025

Summary

  • install the legacy rsync/rsyncd shims under /usr/libexec/oc-rsync to avoid direct file conflicts
  • register the compatibility shims through update-alternatives on Debian-based systems via maintainer scripts
  • hook RPM installations into the alternatives system so oc-rsync can coexist with upstream packages

Testing

  • not run (not requested)

https://chatgpt.com/codex/tasks/task_e_69056b36da6483238a653b2f57b32db5

@oferchen oferchen merged commit a08501b into master Nov 1, 2025
@oferchen oferchen deleted the enable-side-by-side-installation-of-rsync branch November 1, 2025 02:20
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.
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant