What are the risks of --insecure-links?

Chris Green cl at isbd.net
Wed Sep 30 09:52:43 UTC 2026


My several (mostly Debian) systems have just upgraded rsync to version
3.5 and, as a result, I'm getting quite a few warnings like the
following:-

    refusing to follow a symlink owned by an untrusted user; use --insecure-links locally or "insecure links = yes" in a daemon module ONLY if every path component is trusted

These are all 'my' systems and are on my home LAN behind a reasonably
secure firewall.

What are the risks if I add "--insecure-links" to my rsync backups? I am
the only user on nearly all these systems, the only other user is my wife
who is generally a 'trusted' user! :-)


Also, is there any easy way to find the symlinks causing the warning? 
All these are incremental backups using --link-dest and have pre
backup and post backup scripts so it's not easy to run just the rsync
itself from the command line.  Would adding '--dry-run --progress' be
likely to show which symlinks are causing the problem (without
screwing up my incremental backup sequence)?

The error is only appearing a few times (just once on some backups, maybe
a dozen on others) so it may be that I can find and get rid of (or ignore
using exclude) the symlinks causing the warnings.

-- 
Chris Green



More information about the rsync mailing list