What are the risks of --insecure-links?

[rsync.project]

Hi Chris,

This error happens because the symlink you are operating with is an
untrusted symlink. Untrusted symlink is a symlink which is not owned by
root or the user running the process if the process is local, otherwise if
the process is daemon it should not follow any link outside the daemon
tree. —insecure-links will follow non-trusted symlinks normally. By
applying —insecure-links any user have permissions to the syncing tree (src
or dest) can redirect the transfer if he planted symlink inside the
operating tree (rsync -a src/ dest/). If you don’t have any untrusted users
on the system it’s ok to use —insecure-links , but it’s better to lchown
the symlink with a trusted UID to avoid any issues.

 Cheers,
 Seks99x
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/rsync/attachments/20260930/c2164609/attachment.htm>