chrome_sandbox_nacl_selinux(8)				SELinux Policy chrome_sandbox_nacl			    chrome_sandbox_nacl_selinux(8)

NAME

       chrome_sandbox_nacl_selinux - Security Enhanced Linux Policy for the chrome_sandbox_nacl processes

DESCRIPTION

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

       The chrome_sandbox_nacl processes execute with the chrome_sandbox_nacl_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 chrome_sandbox_nacl_t

ENTRYPOINTS

       The chrome_sandbox_nacl_t SELinux type can be entered via the bin_t, usr_t, chrome_sandbox_nacl_exec_t file types.

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

       All executeables with the default executable label, usually stored in /usr/bin and /usr/sbin.  /usr/.*, /opt/.*,  /emul/.*,  /export(/.*)?,
       /usr/doc(/.*)?/lib(/.*)?,  /usr/inclu.e(/.*)?,  /usr/share/doc(/.*)?/README.*, /usr, /opt, /emul, /opt/google/chrome/nacl_helper_bootstrap,
       /usr/lib/chromium-browser/nacl_helper_bootstrap

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

       The following process types are defined for chrome_sandbox_nacl:

       chrome_sandbox_nacl_t

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

BOOLEANS

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

       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

MANAGED FILES

       The  SELinux  process  type chrome_sandbox_nacl_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.

       chrome_sandbox_home_t

	    /home/[^/]*/.cache/chromium(/.*)?
	    /home/[^/]*/.cache/google-chrome(/.*)?

       chrome_sandbox_tmpfs_t

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

       STANDARD FILE CONTEXT

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

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

       The following file types are defined for chrome_sandbox_nacl:

       chrome_sandbox_nacl_exec_t

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

       Paths:
	    /opt/google/chrome/nacl_helper_bootstrap, /usr/lib/chromium-browser/nacl_helper_bootstrap

       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.

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 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.

AUTHOR

       This manual page was auto-generated using sepolicy manpage .

SEE ALSO

       selinux(8), chrome_sandbox_nacl(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8)

chrome_sandbox_nacl						     14-06-10					    chrome_sandbox_nacl_selinux(8)