fenced_selinux man page on Oracle

Man page or keyword search:  
man Server   33470 pages
apropos Keyword Search (all sections)
Output format
Oracle logo
[printable version]

fenced_selinux(8)	     SELinux Policy fenced	     fenced_selinux(8)

NAME
       fenced_selinux  -  Security  Enhanced  Linux Policy for the fenced pro‐
       cesses

DESCRIPTION
       Security-Enhanced Linux	secures	 the  fenced  processes	 via  flexible
       mandatory access control.

       The  fenced  processes  execute with the fenced_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 fenced_t

ENTRYPOINTS
       The  fenced_t  SELinux  type  can be entered via the fenced_exec_t file
       type.

       The default entrypoint paths for the fenced_t domain are the following:

       /usr/sbin/fenced,      /usr/sbin/fence_node,	 /usr/sbin/fence_tool,
       /usr/sbin/fence_virtd, /usr/sbin/fence_sanlockd

PROCESS TYPES
       SELinux defines process types (domains) for each process running on the
       system

       You can see the context of a process using the -Z option to ps

       Policy governs the access confined processes have  to  files.   SELinux
       fenced  policy  is  very	 flexible allowing users to setup their fenced
       processes in as secure a method as possible.

       The following process types are defined for fenced:

       fenced_t

       Note: semanage permissive -a fenced_t can be used to make  the  process
       type  fenced_t  permissive.  SELinux does not deny access to permissive
       process types, but the AVC (SELinux denials) messages are still	gener‐
       ated.

BOOLEANS
       SELinux	policy is customizable based on least access required.	fenced
       policy is extremely flexible and has several booleans that allow you to
       manipulate the policy and run fenced with the tightest access possible.

       If you want to determine whether fenced can connect to the TCP network,
       you must turn on the fenced_can_network_connect	boolean.  Disabled  by
       default.

       setsebool -P fenced_can_network_connect 1

       If  you	want to determine whether fenced can use ssh, you must turn on
       the fenced_can_ssh boolean. Disabled by default.

       setsebool -P fenced_can_ssh 1

       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 authlo‐
       gin_nsswitch_use_ldap boolean. Disabled by default.

       setsebool -P authlogin_nsswitch_use_ldap 1

       If you want to allow cluster administrative cluster  domains  memcheck-
       amd64-	to   use  executable  memory,  you  must  turn	on  the	 clus‐
       ter_use_execmem boolean. Disabled by default.

       setsebool -P cluster_use_execmem 1

       If you want to allow all daemons to write corefiles to /, you must turn
       on the daemons_dump_core boolean. Disabled by default.

       setsebool -P daemons_dump_core 1

       If  you	want  to enable cluster mode for daemons, you must turn on the
       daemons_enable_cluster_mode boolean. Enabled by default.

       setsebool -P daemons_enable_cluster_mode 1

       If you want to allow all daemons to use tcp wrappers, you must turn  on
       the daemons_use_tcp_wrapper boolean. Disabled by default.

       setsebool -P daemons_use_tcp_wrapper 1

       If  you	want to allow all daemons the ability to read/write terminals,
       you must turn on the daemons_use_tty boolean. Disabled by default.

       setsebool -P daemons_use_tty 1

       If you want to deny any process from ptracing or	 debugging  any	 other
       processes,  you	must  turn  on	the  deny_ptrace  boolean.  Enabled by
       default.

       setsebool -P deny_ptrace 1

       If you want to allow all domains to use other domains file descriptors,
       you must turn on the domain_fd_use boolean. Enabled by default.

       setsebool -P domain_fd_use 1

       If  you	want to allow all domains to have the kernel load modules, you
       must  turn  on  the  domain_kernel_load_modules	boolean.  Disabled  by
       default.

       setsebool -P domain_kernel_load_modules 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 enable reading of urandom for all domains, you must turn
       on the global_ssp boolean. Disabled by default.

       setsebool -P global_ssp 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

NSSWITCH DOMAIN
       If you want to allow users to resolve user passwd entries directly from
       ldap rather then using a sssd server for the fenced_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
       fenced_t, you must turn on the kerberos_enabled boolean.

       setsebool -P kerberos_enabled 1

MANAGED FILES
       The  SELinux  process  type  fenced_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_log

       cluster_tmpfs_t

       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/cpglockd.pid
	    /var/run/corosync.pid
	    /var/run/rgmanager.pid
	    /var/run/cluster/rgmanager.sk

       fenced_lock_t

	    /var/lock/fence_manual.lock

       fenced_tmp_t

       fenced_tmpfs_t

       fenced_var_run_t

	    /var/run/fence.*
	    /var/run/cluster/fence_scsi.*
	    /var/run/cluster/fenced_override

       root_t

	    /
	    /initrd

       snmpd_var_lib_t

	    /var/agentx(/.*)?
	    /var/net-snmp(/.*)
	    /var/lib/snmp(/.*)?
	    /var/net-snmp(/.*)?
	    /var/lib/net-snmp(/.*)?
	    /var/spool/snmptt(/.*)?
	    /usr/share/snmp/mibs/.index

FILE CONTEXTS
       SELinux requires files to have an extended attribute to define the file
       type.

       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	fenced	policy	is very flexible allowing users to setup their
       fenced processes in as secure a method as possible.

       STANDARD FILE CONTEXT

       SELinux defines the file context types for the fenced, 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 fenced_exec_t '/srv/fenced/content(/.*)?'
       restorecon -R -v /srv/myfenced_content

       Note:  SELinux  often  uses  regular expressions to specify labels that
       match multiple files.

       The following file types are defined for fenced:

       fenced_exec_t

       - Set files with the fenced_exec_t type, if you want to	transition  an
       executable to the fenced_t domain.

       Paths:
	    /usr/sbin/fenced,	 /usr/sbin/fence_node,	 /usr/sbin/fence_tool,
	    /usr/sbin/fence_virtd, /usr/sbin/fence_sanlockd

       fenced_lock_t

       - Set files with the fenced_lock_t type, if you want to treat the files
       as fenced lock data, stored under the /var/lock directory

       fenced_tmp_t

       -  Set  files  with  the fenced_tmp_t type, if you want to store fenced
       temporary files in the /tmp directories.

       fenced_tmpfs_t

       - Set files with the fenced_tmpfs_t type, if you want to	 store	fenced
       files on a tmpfs file system.

       fenced_var_log_t

       -  Set  files  with the fenced_var_log_t type, if you want to treat the
       data as fenced var log data, usually stored under the  /var/log	direc‐
       tory.

       fenced_var_run_t

       -  Set  files  with the fenced_var_run_t type, if you want to store the
       fenced files under the /run or /var/run directory.

       Paths:
	    /var/run/fence.*,  /var/run/cluster/fence_scsi.*,	/var/run/clus‐
	    ter/fenced_override

       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 data‐
       base.  You will need to use restorecon to apply the labels.

COMMANDS
       semanage fcontext can also be used to manipulate default	 file  context
       mappings.

       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  pol‐
       icy modules.

       semanage boolean can also be used to manipulate the booleans

       system-config-selinux is a GUI tool available to customize SELinux pol‐
       icy settings.

AUTHOR
       This manual page was auto-generated using sepolicy manpage .

SEE ALSO
       selinux(8), fenced(8),  semanage(8),  restorecon(8),  chcon(1),	sepol‐
       icy(8) , setsebool(8)

fenced				   14-05-08		     fenced_selinux(8)
[top]

List of man pages available for Oracle

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net