chrome_..._selinux(8)

πŸ“¦
version 20250627+git412.dbf877ab7 Β· 7 versions
, in opensuse-leap 16.0

πŸ’– NAME πŸ’–

okay bestie, welcome to the chrome_..._selinux(8) manual page β€” the SELinux Policy for chrome_sandbox_nacl, and the main character here is chrome_sandbox_nacl_selinux: Security Enhanced Linux Policy for the chrome_sandbox_nacl processes. slay. πŸ’…

✨ DESCRIPTION ✨

Security-Enhanced Linux secures the chrome_sandbox_nacl processes via flexible mandatory access control. no cap, that's the whole vibe.

The chrome_sandbox_nacl processes execute with the chrome_sandbox_nacl_t SELinux type. Wanna check if you've got these processes running? run 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 literally:

  • All executables with the default executable label, usually stored in /usr/bin and /usr/sbin.
  • /opt/.*
  • /usr/.*
  • /hana(/.*)?
  • /emul/.*
  • /export(/.*)?
  • /ostree(/.*)?
  • /usr/doc(/.*)?/lib(/.*)?
  • /usr/inclu.e(/.*)?
  • /usr/share/rpm(/.*)?
  • /usr/share/doc(/.*)?/README.*
  • /usr/lib/modules(/.*)/vmlinuz
  • /usr/lib/modules(/.*)/sysctl.conf
  • /usr/lib/modules(/.*)/initramfs.img
  • /usr/lib/sysimage(/.*)?
  • /usr/lib/ostree-boot(/.*)?
  • /opt
  • /usr
  • /emul
  • /opt/google/chrome[^/]*/nacl_helper_bootstrap
  • /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.

πŸ“ 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/[^/]+/.config/chromium(/.*)?
    • /home/[^/]+/.cache/google-chrome(/.*)?
    • /home/[^/]+/.cache/google-chrome-unstable(/.*)?
  • 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 different paths, you need to execute the semanage command to specify 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
      • /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.
  • 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 πŸ‘€


okay that's the whole page, bestie β€” sending you off with the chrome_sandbox_nacl source/version, dated 26-10-06, under the chrome_..._selinux(8) manual name. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from