Security-Enhanced Linux secures the cupsd_config processes via flexible mandatory access control.
If you want to allow users to resolve user passwd entries directly from ldap rather then using a sssd serve for the cupsd_config_t, you must turn on the authlogin_nsswitch_use_ldap boolean.
setsebool -P authlogin_nsswitch_use_ldap 1
If you want to allow confined applications to run with kerberos for the cupsd_config_t, you must turn on the kerberos_enabled boolean.
setsebool -P kerberos_enabled 1
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 cupsd_config policy is very flexible allowing users to setup their cupsd_config processes in as secure a method as possible.
The following file types are defined for cupsd_config:
cupsd_config_exec_t
- Set files with the cupsd_config_exec_t type, if you want to transition an executable to the cupsd_config_t domain.
cupsd_config_var_run_t
- Set files with the cupsd_config_var_run_t type, if you want to store the cupsd config files under the /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.
You can see the context of a process using the -Z option to psP Policy governs the access confined processes have to files. SELinux cupsd_config policy is very flexible allowing users to setup their cupsd_config processes in as secure a method as possible.
The following process types are defined for cupsd_config:
cupsd_config_t
Note: semanage permissive -a PROCESS_TYPE can be used to make a process type permissive. Permissive process types are not denied access by SELinux. AVC messages will still be generated.
The SELinux user type cupsd_config_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.
cupsd_config_var_run_t
/var/run/udev-configure-printer(/.*)?
cupsd_etc_t
/etc/cups(/.*)?
/usr/share/cups(/.*)?
cupsd_log_t
/var/log/cups(/.*)?
/usr/Brother/fax/.*.log.*
/var/log/turboprint.*
cupsd_rw_etc_t
/etc/printcap.*
/etc/cups/ppd(/.*)?
/usr/Brother/(.*/)?inf(/.*)?
/usr/Printer/(.*/)?inf(/.*)?
/usr/lib/bjlib(/.*)?
/var/lib/iscan(/.*)?
/var/cache/cups(/.*)?
/etc/cups/certs/.*
/etc/cups/lpoptions.*
/var/cache/foomatic(/.*)?
/etc/cups/cupsd.conf.*
/var/lib/cups/certs/.*
/opt/gutenprint/ppds(/.*)?
/opt/brother/Printers(.*/)?inf(/.*)?
/etc/cups/classes.conf.*
/etc/cups/printers.conf.*
/etc/cups/subscriptions.*
/usr/local/linuxprinter/ppd(/.*)?
/var/cache/alchemist/printconf.*
/etc/alchemist/namespace/printconf(/.*)?
/etc/cups/certs
/etc/cups/ppds.dat
/var/lib/cups/certs
/usr/share/foomatic/db/oldprinterids
cupsd_tmp_t
user_tmp_t
/var/run/user(/.*)?
/tmp/gconfd-.*