]> git.ipfire.org Git - thirdparty/rsync.git/commit
testsuite: probe RESOLVE_BENEATH support functionally for the #715 test
authorAndrew Tridgell <andrew@tridgell.net>
Sat, 23 May 2026 22:12:39 +0000 (08:12 +1000)
committerAndrew Tridgell <andrew@tridgell.net>
Sun, 24 May 2026 02:31:52 +0000 (12:31 +1000)
commitb0ba699031a697e816091cfb805be3eec2bfc6d7
treea40ae74e51a25e688d54df59113a91b627c4b21c
parente57c7f5d877904608454dbb61a302ceb977b1571
testsuite: probe RESOLVE_BENEATH support functionally for the #715 test

Add resolve_beneath_supported() to rsyncfns: it functionally probes whether the
rsync binary can follow an in-tree directory symlink under its secure resolver
(an initial transfer plus a delta update through a dir-symlink, the operation
issue #715 is about). This tracks the actual binary instead of a platform name.

Use it in symlink-dirlink-basis_test.py in place of the SunOS/OpenBSD/NetBSD/
Cygwin name check: it skips on those platforms too, and additionally on
Linux < 5.6, a seccomp-blocked openat2, and the new --disable-openat2 build,
where the portable O_NOFOLLOW fallback rejects the in-tree symlink.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
testsuite/rsyncfns.py
testsuite/symlink-dirlink-basis_test.py