Implement checksum-aware incremental synchronization #203
Reference in New Issue
Block a user
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?
Severity
High
Description
The CLI accepts --checksum and the scanner stores the option, but incremental matching still compares only size and second-resolution mtime. Same-size content replaced while preserving mtime can remain stale. Related parsed rsync options such as --update, --append, and --append-verify also have no transfer behavior.
Location
Validation
Create a destination file, replace source content with same length, restore its mtime, then run --incremental --checksum and verify the destination. Inspect transfer paths for reads of update/append/append_verify.
Suggested implementation
Negotiate and compare a cryptographic/content checksum when requested, then implement documented update and append semantics or reject unsupported flags rather than silently ignoring them. Add TCP/TLS integration tests.