3 Commits

Include renames

Author	SHA1	Message	Date
TapTap	cbb09e41ab	identity: fix use-after-free in --usermap/--groupmap parse error path ... identity_parse_map freed the str_dup'd list before logging the offending rule ( points into that buffer), causing an invalid read caught by CI valgrind (MSAN/MSAN-style; the ONLY definite valgrind error in the suite). Log before freeing. valgrind now reports 0 errors / 0 definite leaks in both the parent and the forked wire-roundtrip child.	2026-09-08 18:49:23 +02:00
TapTap	b283c8084c	identity: keep --numeric-ids in the activate set (-M --numeric-ids) ... identity_active_enabled() only gates identity_apply_ownership, which runs only when metadata is present, so --numeric-ids must stay in the set: combined with -M it activates raw-id application, while a standalone --numeric-ids (no ownership-affecting flag) carries no metadata and correctly stays inert. My earlier review fix removed it and broke 'owner not applied' for -M --numeric-ids (uid 0 instead of the source ids). Revert that removal.	2026-09-08 18:37:07 +02:00
TapTap	53ce00b830	identity mapping: --numeric-ids / --usermap / --groupmap / --chown ... Receiver-side ownership application, opt-in and privilege-gated: - OFF for every existing transfer (plain -M/--preserve still never applies ownership); only triggers on an explicit identity flag + receiver permission. - EPERM/EACCES warn-and-continue (never aborts); other fchown errors escalate. - fd-relative fchown after the file is written (symlink-safe, confined). - New src/shared/identity.{c,h}; config fields numeric_ids / chown uid/gid / usermap + groupmap id-pair tables cross the wire; PROTOCOL_VERSION 2.10.0 -> 2.11.0. CLI in client_cli.c; per-connection snapshot in server.c. - Review fixes: EPERM/EACCES-only warn-and-continue, prominent root-receiver notice, identity_clear_active on early server error paths, --numeric-ids kept inert standalone (removed from activation trigger set).	2026-09-08 18:23:43 +02:00