Security-Enhanced Linux secures the winbind processes via flexible mandatory access control.
The winbind processes execute with the winbind_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 winbind_t
The winbind_t SELinux type can be entered via the winbind_exec_t file type.
The default entrypoint paths for the winbind_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 winbind policy is very flexible allowing users to setup their winbind processes in as secure a method as possible.
The following process types are defined for winbind:
winbind_t, winbind_helper_t
Note: semanage permissive -a winbind_t can be used to make the process type winbind_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 users to resolve user passwd entries directly from ldap rather then using a sssd server, you must turn on the authlogin_nsswitch_use_ldap boolean. Disabled by default.
setsebool -P authlogin_nsswitch_use_ldap 1
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
If you want to allow confined applications to use nscd shared memory, you must turn on the nscd_use_shm boolean. Enabled by default.
setsebool -P nscd_use_shm 1
The SELinux process type winbind_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.
auth_cache_t
/var/cache/coolkey(/.*)?
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
ctdbd_var_lib_t
/var/lib/ctdb(/.*)?
/var/lib/ctdbd(/.*)?
faillog_t
/var/log/btmp.*
/var/log/faillog.*
/var/log/tallylog.*
/var/run/faillock(/.*)?
krb5_host_rcache_t
/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
krb5_keytab_t
/etc/krb5.keytab
/etc/krb5kdc/kadm5.keytab
/var/kerberos/krb5kdc/kadm5.keytab
root_t
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
samba_log_t
/var/log/samba(/.*)?
samba_secrets_t
/etc/samba/smbpasswd
/etc/samba/passdb.tdb
/etc/samba/MACHINE.SID
/etc/samba/secrets.tdb
samba_var_t
/var/nmbd(/.*)?
/var/lib/samba(/.*)?
/var/cache/samba(/.*)?
smbd_tmp_t
smbd_var_run_t
/var/run/samba(/.*)?
/var/run/samba/smbd.pid
/var/run/samba/brlock.tdb
/var/run/samba/locking.tdb
/var/run/samba/gencache.tdb
/var/run/samba/sessionid.tdb
/var/run/samba/share_info.tdb
/var/run/samba/connections.tdb
user_home_t
/home/[^/]+/.+
user_tmp_t
/dev/shm/mono.*
/var/run/user(/.*)?
/tmp/.ICE-unix(/.*)?
/tmp/.X11-unix(/.*)?
/dev/shm/pulse-shm.*
/tmp/.X0-lock
/tmp/hsperfdata_root
/var/tmp/hsperfdata_root
/home/[^/]+/tmp
/home/[^/]+/.tmp
/tmp/gconfd-[^/]+
winbind_log_t
winbind_var_run_t
/var/run/winbindd(/.*)?
/var/run/samba/winbindd(/.*)?
/var/lib/samba/winbindd_privileged(/.*)?
/var/cache/samba/winbindd_privileged(/.*)?
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 winbind policy is very flexible allowing users to setup their winbind processes in as secure a method as possible.
STANDARD FILE CONTEXT
SELinux defines the file context types for the winbind, if you wanted to store files with these types in a diffent paths, you need to execute the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk.
semanage fcontext -a -t winbind_var_run_t '/srv/mywinbind_content(/.*)?'
restorecon -R -v /srv/mywinbind_content
Note: SELinux often uses regular expressions to specify labels that match multiple files.
The following file types are defined for winbind:
winbind_exec_t
- Set files with the winbind_exec_t type, if you want to transition an executable to the winbind_t domain.
winbind_helper_exec_t
- Set files with the winbind_helper_exec_t type, if you want to transition an executable to the winbind_helper_t domain.
winbind_log_t
- Set files with the winbind_log_t type, if you want to treat the data as winbind log data, usually stored under the /var/log directory.
winbind_var_run_t
- Set files with the winbind_var_run_t type, if you want to store the winbind files under the /run or /var/run directory.
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.