sandbox_net_selinux(8)

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

🌸 NAME 🌸

<pink>sandbox_net_selinux(8)</pink> is the manual page for <hotpink>Security Enhanced Linux Policy</hotpink> for the <cyan>sandbox_net</cyan> processes. Bestie, this is the SELinux policy guide for that whole sandbox_net situation. πŸ’…


✨ DESCRIPTION ✨

Security-Enhanced Linux secures the <purple>sandbox_net</purple> processes via flexible mandatory access control. It’s giving locked-down-but-customizable, fr fr. πŸ”

The <cyan>sandbox_net</cyan> processes execute with the <mint>sandbox_net_t</mint> SELinux type. You can check if you have these processes running by executing the <yellow>ps</yellow> command with the <yellow>-Z</yellow> qualifier. Easy vibe check:

ps -eZ | grep sandbox_net_t

🫢 PROCESS TYPES 🫢

SELinux defines process types (domains) for each process running on the system. Okay so that’s the whole domain situation. πŸ‘‘

You can see the context of a process using the <yellow>-Z</yellow> option to <yellow>ps</yellow>.

Policy governs the access confined processes have to files. SELinux <purple>sandbox_net</purple> policy is very flexible allowing users to setup their <cyan>sandbox_net</cyan> processes in as secure a method as possible. Iconic flexibility behavior. ✨

The following process types are defined for <purple>sandbox_net</purple>:

  • <mint>sandbox_net_t</mint>
  • <mint>sandbox_net_client_t</mint>
Note: <yellow>semanage permissive -a sandbox_net_t</yellow> can be used to make the process type <mint>sandbox_net_t</mint> permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it’s permissive but still chatty about it. πŸ’€

πŸ”’ MCS Constrained πŸ”’

The SELinux process type <mint>sandbox_net_t</mint> is an MCS (Multi Category Security) constrained type. Sometimes this separation is referred to as <purple>sVirt</purple>. These types are usually used for securing multi-tenant environments, such as virtualization, containers or separation of users. The tools used to launch MCS types, pick out a different MCS label for each process group. It’s giving separate lil’ VIP sections for processes. πŸŽ€

For example one process might be launched with <cyan>sandbox_net_t:s0:c1,c2</cyan>, and another process launched with <cyan>sandbox_net_t:s0:c3,c4</cyan>. The SELinux kernel only allows these processes can only write to content with a matching MCS label, or a MCS Label of <cyan>s0</cyan>. A process running with the MCS level of <cyan>s0:c1,c2</cyan> is not allowed to write to content with the MCS label of <cyan>s0:c3,c4</cyan>. No crossing the velvet rope, bestie. 🚫✨


πŸ’– BOOLEANS πŸ’–

SELinux policy is customizable based on least access required. <purple>sandbox_net</purple> policy is extremely flexible and has several booleans that allow you to manipulate the policy and run <cyan>sandbox_net</cyan> with the tightest access possible. Choose-your-own-adventure, but make it security. πŸ¦‹

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 <mint>deny_execmem</mint> boolean. Disabled by default.

setsebool -P deny_execmem 1

If you want to allow system to run with NIS, you must turn on the <mint>nis_enabled</mint> boolean. Disabled by default.

setsebool -P nis_enabled 1

πŸ—‚οΈ MANAGED FILES πŸ—‚οΈ

The SELinux process type <mint>sandbox_net_t</mint> 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. Like, SELinux said what it said, but DAC is still in the group chat. 😌

  • fusefs_t
    • /run/user/[0-9]+/gvfs
  • 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
  • mozilla_plugin_tmpfs_t
  • sandbox_file_t
  • sandbox_net_client_tmpfs_t
  • security_t
    • /selinux

πŸ› οΈ COMMANDS πŸ› οΈ

  • <yellow>semanage fcontext</yellow> can also be used to manipulate default file context mappings.
  • <yellow>semanage permissive</yellow> can also be used to manipulate whether or not a process type is permissive.
  • <yellow>semanage module</yellow> can also be used to enable/disable/install/remove policy modules.
  • <yellow>semanage boolean</yellow> can also be used to manipulate the booleans.
  • <yellow>system-config-selinux</yellow> is a GUI tool available to customize SELinux policy settings.

πŸ‘‘ AUTHOR πŸ‘‘

This manual page was auto-generated using <yellow>sepolicy manpage</yellow> . Automatic queen behavior. ✨


🌈 SEE ALSO 🌈


That’s the whole vibe check, bestie πŸ’« β€” the footer energy is <purple>sandbox_net</purple>, dated <cyan>26-10-06</cyan>, and it’s the <pink>sandbox_net_selinux(8)</pink> manual. Stay secure and slay! πŸ’…βœ¨πŸ«Ά

πŸ“¦ where this page comes from