sandbox_...r_selinux(8)

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

πŸ’– sandbox_xserver_selinux(8) β€” the SELinux glow-up for your xserver besties πŸ’–

okay so real talk, this is the manual page for sandbox_xserver_selinux, and it's literally all about keeping your sandboxed xserver processes safe and slaying. periodt. let's get into it ✨


✨ NAME ✨

sandbox_xserver_selinux β€” Security Enhanced Linux Policy for the sandbox_xserver processes πŸŽ€


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the sandbox_xserver processes via flexible mandatory access control. yes bestie, mandatory. not optional. it's giving authority. πŸ‘‘

The sandbox_xserver processes execute with the sandbox_xserver_t SELinux type. wanna check if you've got these processes running? just run the ps command with the -Z qualifier, iykyk πŸ¦‹

like, for example:

ps -eZ | grep sandbox_xserver_t

there she is. she's running. πŸ’…


πŸšͺ ENTRYPOINTS πŸšͺ

so the sandbox_xserver_t SELinux type can be entered via the xserver_exec_t file type. that's the doorway, the entryway, the main character entrance. πŸŽ€

the default entrypoint paths for the sandbox_xserver_t domain are literally these exact ones, no cap:

/usr/bin/nvidia.*, /usr/bin/Xair, /usr/bin/Xorg, /usr/bin/Xvnc,
/usr/bin/Xephyr, /usr/bin/x11vnc, /usr/X11R6/bin/X, /usr/bin/Xwayland,
/usr/X11R6/bin/Xorg, /usr/X11R6/bin/Xipaq, /usr/libexec/Xorg.bin,
/usr/X11R6/bin/XFree86, /usr/libexec/Xorg.wrap, /usr/X11R6/bin/Xwrapper,
/usr/libexec/gsd-backlight-helper

those are the vibes. do not lose them. 🌈


πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (aka domains) for each process running on the system. it's giving organized. it's giving structured. πŸ’œ

you can see the context of a process using the -Z option to ps. yes, again with the -Z. iconic. 🌟

Policy governs the access these confined processes have to files. the SELinux sandbox_xserver policy is very flexible, fr fr, allowing users to set up their sandbox_xserver processes in as secure a method as possible. safe and secure, slay. πŸ”₯

the following process types are defined for sandbox_xserver:

sandbox_xserver_t
NOTE: semanage permissive -a sandbox_xserver_t can be used to make the process type sandbox_xserver_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so she's not blocking anything, but she's still watching. πŸ’€

πŸŽ›οΈ BOOLEANS πŸŽ›οΈ

SELinux policy is customizable based on least access required. the sandbox_xserver policy is extremely flexible and has several booleans that allow you to manipulate the policy and run sandbox_xserver with the tightest access possible. tightest access, bestie. we love a locked-down ship. 🫢

  • if you want to deny user domains applications to map a memory region as both executable and writable β€” this is dangerous and the executable should be reported in bugzilla β€” you must turn on the deny_execmem boolean. Disabled by default. 😭 dangerous, we said it, don't @ me.
setsebool -P deny_execmem 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 regular users direct dri device access, you must turn on the selinuxuser_direct_dri_enabled boolean. Disabled by default.
setsebool -P selinuxuser_direct_dri_enabled 1
  • if you want to support fusefs home directories, you must turn on the use_fusefs_home_dirs boolean. Disabled by default.
setsebool -P use_fusefs_home_dirs 1
  • if you want to support NFS home directories, you must turn on the use_nfs_home_dirs boolean. Enabled by default. yes you read that right, enabled by default bestie, she's already on. πŸ’…
setsebool -P use_nfs_home_dirs 1
  • if you want to support SAMBA home directories, you must turn on the use_samba_home_dirs boolean. Disabled by default.
setsebool -P use_samba_home_dirs 1
  • if you want to allows clients to write to the X server shared memory segments, you must turn on the xserver_clients_write_xshm boolean. Disabled by default.
setsebool -P xserver_clients_write_xshm 1

πŸ“ MANAGED FILES πŸ“

The SELinux process type sandbox_xserver_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. so like, SELinux is cool with it, but the Unix permissions still get a say. teamwork. 🫢

krb5_host_rcache_t

/var/tmp/krb5_0.rcache2
/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

sandbox_file_t

(no paths listed, she just exists, and we respect her 🌸)

sandbox_xserver_tmpfs_t

(again, no paths, just vibes ✨)

security_t

/selinux

user_fonts_cache_t

/root/.fontconfig(/.*)?
/root/.fonts/auto(/.*)?
/root/.fonts.cache-.*
/root/.cache/fontconfig(/.*)?
/home/[^/]+/.fontconfig(/.*)?
/home/[^/]+/.fonts/auto(/.*)?
/home/[^/]+/.fonts.cache-.*
/home/[^/]+/.cache/fontconfig(/.*)?

font cache slay. πŸŽ€


πŸ’» 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. yes, a GUI. for when you want to point and click instead of type. main character energy πŸ’…

πŸ”₯ AUTHOR πŸ”₯

This manual page was auto-generated using sepolicy manpage. no cap, the machines did it. πŸ€–βœ¨


🌈 SEE ALSO 🌈

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

the whole friend group, periodt. πŸ«ΆπŸ’–


and that's the whole page, bestie! auto-generated with love on 26-10-06 for sandbox_xserver. now go forth and keep your xserver sandboxed and your booleans on point. πŸ’œπŸ¦‹βœ¨

πŸ“¦ where this page comes from