Security-Enhanced Linux secures the jabberd_router processes via flexible mandatory access control.
The jabberd_router processes execute with the jabberd_router_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.
For example:
ps -eZ | grep jabberd_router_t
The jabberd_router_t SELinux type can be entered via the jabberd_router_exec_t file type.
The default entrypoint paths for the jabberd_router_t domain are the following:
You can see the context of a process using the -Z option to psP Policy governs the access confined processes have to files. SELinux jabberd_router policy is very flexible allowing users to setup their jabberd_router processes in as secure a method as possible.
The following process types are defined for jabberd_router:
jabberd_router_t
Note: semanage permissive -a jabberd_router_t can be used to make the process type jabberd_router_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.
If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.
setsebool -P fips_mode 1
If you want to allow confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. Enabled by default.
setsebool -P kerberos_enabled 1
If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.
setsebool -P nis_enabled 1
The SELinux process type jabberd_router_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.
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
/var/run/crm(/.*)?
/var/run/cman_.*
/var/run/rsctmp(/.*)?
/var/run/aisexec.*
/var/run/heartbeat(/.*)?
/var/run/corosync-qnetd(/.*)?
/var/run/corosync-qdevice(/.*)?
/var/run/corosync.pid
/var/run/cpglockd.pid
/var/run/rgmanager.pid
/var/run/cluster/rgmanager.sk
jabberd_var_lib_t
/var/lib/jabberd(/.*)?
root_t
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
You can see the context of a file using the -Z option to lsP Policy governs the access confined processes have to these files. SELinux jabberd_router policy is very flexible allowing users to setup their jabberd_router processes in as secure a method as possible.
The following file types are defined for jabberd_router:
jabberd_router_exec_t
- Set files with the jabberd_router_exec_t type, if you want to transition an executable to the jabberd_router_t domain.
Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels.
semanage permissive can also be used to manipulate whether or not a process type is permissive.
semanage module can also be used to enable/disable/install/remove policy modules.
semanage boolean can also be used to manipulate the booleans
system-config-selinux is a GUI tool available to customize SELinux policy settings.