rsync_selinux(8)
β¨ rsync_selinux β¨
Okay bestie, you found the SELinux policy page for rsync β the manual name is rsync_selinux(8) btw, in case you were wondering what you're even reading π
πΈ NAME πΈ
rsync_selinux β Security Enhanced Linux Policy for the rsync processes. Yup, that's the whole vibe. It's literally the SELinux rulebook for how rsync is allowed to exist on your system π«Ά
β¨ DESCRIPTION β¨
Security-Enhanced Linux secures the rsync processes via flexible mandatory access control. No cap β SELinux is out here being a full-on bodyguard for your rsync stuff π₯
The rsync processes execute with the rsync_t SELinux type. Wanna check if you've got these processes running? Just run the ps command with the -Z qualifier. It's giving detective energy π
For example:
ps -eZ | grep rsync_t
πͺ ENTRYPOINTS πͺ
The rsync_t SELinux type can be entered via the rsync_exec_t file type. So that's the door you gotta walk through to get in, iykyk πͺβ¨
The default entrypoint paths for the rsync_t domain are literally these:
/usr/bin/rsyncd
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. Every single one gets its own little category, iconic behavior honestly π
You can see the context of a process using the -Z option to ps
Policy governs the access confined processes have to files. SELinux rsync policy is very flexible, allowing users to setup their rsync processes in as secure a method as possible. It's all about that tightest-access-possible lifestyle π
The following process types are defined for rsync:
rsync_t
Note:semanage permissive -a rsync_tcan be used to make the process typersync_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's not a free pass β you'll still get receipts of what it's trying to do π
π§ BOOLEANS π§
SELinux policy is customizable based on least access required. rsync policy is extremely flexible and has several booleans that allow you to manipulate the policy and run rsync with the tightest access possible. Booleans are basically lil on/off switches for behaviors β very main character energy, honestly π
- If you want to allow rsync to run as a client, you must turn on the
rsync_clientboolean. Disabled by default.
setsebool -P rsync_client 1
- If you want to allow rsync to execute commands. This is needed on SUSE systems in general, and on other systems in more complex configurations where e.g.
pre-xfer execis used. You must turn on thersync_exec_commandsboolean. Enabled by default.
setsebool -P rsync_exec_commands 1
- If you want to allow rsync to export any files/directories read only, you must turn on the
rsync_export_all_roboolean. Disabled by default.
setsebool -P rsync_export_all_ro 1
- If you want to allow the rsync server to manage all files/directories on the system, you must turn on the
rsync_full_accessboolean. Disabled by default.
setsebool -P rsync_full_access 1
- If you want to allow rsync sys_admin capability. This capability is required to restore files with extended attributes in the "trusted" namespace. You must turn on the
rsync_sys_adminboolean. Disabled by default.
setsebool -P rsync_sys_admin 1
- If you want to dontaudit all daemons scheduling requests (
setsched,sys_nice), you must turn on thedaemons_dontaudit_schedulingboolean. Enabled by default.
setsebool -P daemons_dontaudit_scheduling 1
- If you want to allow all domains to execute in
fips_mode, you must turn on thefips_modeboolean. Enabled by default.
setsebool -P fips_mode 1
- If you want to allow the system to run with NIS, you must turn on the
nis_enabledboolean. Disabled by default.
setsebool -P nis_enabled 1
π PORT TYPES π
SELinux defines port types to represent TCP and UDP ports. Ports are like the lil doors services knock on, and SELinux is keeping track of which ones are allowed π
You can see the types associated with a port by using the following command:
semanage port -l
Policy governs the access confined processes have to these ports. SELinux rsync policy is very flexible, allowing users to setup their rsync processes in as secure a method as possible. Yes bestie, same energy as before β flexibility with security, periodt π«Ά
The following port types are defined for rsync:
rsync_port_t
Default Defined Ports:
tcp 873
udp 873
π MANAGED FILES π
The SELinux process type rsync_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note: the processes UID still need to have DAC permissions. So SELinux ain't overriding regular permissions β everyone's still gotta play by the rules π€
cifs_t
cluster_conf_t
/etc/cluster(/.*)?
cluster_var_lib_t
/var/lib/pcsd(/.*)?
/var/lib/cluster(/.*)?
/var/lib/openais(/.*)?
/var/lib/pengine(/.*)?
/var/lib/corosync(/.*)?
/usr/lib/heartbeat(/.*)?
/var/lib/heartbeat(/.*)?
/var/lib/pacemaker(/.*)?
cluster_var_run_t
/run/crm(/.*)?
/run/cman_.*
/run/rsctmp(/.*)?
/run/aisexec.*
/run/heartbeat(/.*)?
/run/pcsd-ruby.socket
/run/corosync-qnetd(/.*)?
/run/corosync-qdevice(/.*)?
/run/pcsd.socket
/run/corosync.pid
/run/cpglockd.pid
/run/rgmanager.pid
/run/cluster/rgmanager.sk
ecryptfs_t
/home/[^/]+/.Private(/.*)?
/home/[^/]+/.ecryptfs(/.*)?
fusefs_t
/run/user/[0-9]+/gvfs
krb5_host_rcache_t
/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0
nfs_t
non_auth_file_type
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
rsync_log_t
/var/log/rsync.*
rsync_tmp_t
rsync_var_run_t
/run/rsyncd.lock
/run/swift_server.lock
swift_data_t
/srv/node(/.*)?
/var/lib/swift(/.*)?
/srv/loopback-device(/.*)?
swift_lock_t
/run/lock/swift.*
π·οΈ FILE CONTEXTS π·οΈ
SELinux requires files to have an extended attribute to define the file type. It's like a lil name tag but for security labels, obsessed honestly π
You can see the context of a file using the -Z option to ls
Policy governs the access confined processes have to these files. SELinux rsync policy is very flexible, allowing users to setup their rsync processes in as secure a method as possible. Same energy again, bestie β maximum security, maximum flexibility π
π STANDARD FILE CONTEXT π
SELinux defines the file context types for the rsync. If you wanted to store files with these types in different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk.
semanage fcontext -a -t rsync_exec_t '/srv/rsync/content(/.*)?'
restorecon -R -v /srv/myrsync_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex bestie β it's how we match a whole squad of files at once, no cap π₯
The following file types are defined for rsync:
rsync_data_t
- Set files with the
rsync_data_ttype if you want to treat the files as rsync content.
rsync_etc_t
- Set files with the
rsync_etc_ttype if you want to store rsync files in the/etcdirectories.
rsync_exec_t
- Set files with the
rsync_exec_ttype if you want to transition an executable to thersync_tdomain.
rsync_log_t
- Set files with the
rsync_log_ttype if you want to treat the data as rsync log data, usually stored under the/var/logdirectory.
rsync_tmp_t
- Set files with the
rsync_tmp_ttype if you want to store rsync temporary files in the/tmpdirectories.
rsync_var_run_t
- Set files with the
rsync_var_run_ttype if you want to store the rsync files under the/runor/var/rundirectory.
Paths:
/run/rsyncd.lock, /run/swift_server.lock
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels.chconis giving temporary tattoo energy,semanage fcontextis the real permanent deal π
π€ SHARING FILES π€
If you want to share files with multiple domains (Apache, FTP, rsync, Samba), you can set a file context of public_content_t and public_content_rw_t. These contexts allow any of the above domains to read the content. Sharing is caring, bestie π«Ά
If you want a particular domain to write to the public_content_rw_t domain, you must set the appropriate boolean. Gotta flip the right switch for write access π
Allow rsync servers to read the /var/rsync directory by adding the public_content_t file type to the directory and by restoring the file type.
semanage fcontext -a -t public_content_t "/var/rsync(/.*)?"
restorecon -F -R -v /var/rsync
Allow rsync servers to read and write /var/rsync/incoming by adding the public_content_rw_t type to the directory and by restoring the file type. You also need to turn on the rsync_anon_write boolean.
semanage fcontext -a -t public_content_rw_t "/var/rsync/incoming(/.*)?"
restorecon -F -R -v /var/rsync/incoming
setsebool -P rsync_anon_write 1
If you want to allow rsync to modify public files used for public file transfer services β files/directories must be labeled public_content_rw_t β you must turn on the rsync_anon_write boolean.
setsebool -P rsync_anon_write 1
π» COMMANDS π»
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage portcan also be used to manipulate the port definitions.semanage booleancan also be used to manipulate the booleans.
system-config-selinux is a GUI tool available to customize SELinux policy settings. For the besties who prefer a lil clicky-click over the terminal β no judgment here, slay π
βοΈ AUTHOR βοΈ
This manual page was auto-generated using sepolicy manpage . β yes, it made itself. Iconic, honestly π
π SEE ALSO π
selinux(8), rsync(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
Alright bestie, that's the whole page! Stay slay, stay secure, and remember: it's giving rsync_selinux(8) from the rsync manual, dated 26-10-06. Go forth and label those files with confidence π¦β¨π
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms