podsleuth_selinux(8)

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

πŸ’… podsleuth_selinux β€” bestie edition

okay so this is the podsleuth_selinux page from the SELinux Policy podsleuth manual β€” section 8, obviously β€” and it's literally all about how Security-Enhanced Linux handles the podsleuth processes. grab a strawberry drink, we're doing this πŸ“


✨ NAME ✨

podsleuth_selinux β€” the Security Enhanced Linux Policy for the podsleuth processes. that's it, that's the vibe.


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the podsleuth processes via flexible mandatory access control. yes, mandatory. it's giving strict parent energy but make it security πŸ’…

the podsleuth processes execute with the podsleuth_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier. like so:

ps -eZ | grep podsleuth_t

that's the whole vibe check, bestie. run it, see what's up πŸ”₯


πŸ¦‹ ENTRYPOINTS πŸ¦‹

the podsleuth_t SELinux type can be entered via the podsleuth_exec_t file type. that's the doorway, okay? that's the entrance. main character entrance energy.

the default entrypoint paths for the podsleuth_t domain are literally these:

/usr/bin/podsleuth, /usr/libexec/hal-podsleuth

no cap. those two. πŸ’–


πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system. like, every process gets its own little identity. iconic.

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

policy governs the access confined processes have to files. SELinux podsleuth policy is very flexible, allowing users to setup their podsleuth processes in as secure a method as possible. flexible and secure? we love a multitasker ✨

the following process types are defined for podsleuth:

  • podsleuth_t
Note: semanage permissive -a podsleuth_t can be used to make the process type podsleuth_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it stops blocking but it's definitely still telling on you 😭

πŸŽ€ BOOLEANS πŸŽ€

SELinux policy is customizable based on least access required. podsleuth policy is extremely flexible and has several booleans that allow you to manipulate the policy and run podsleuth with the tightest access possible. tightest access = the outfit that fits exactly right, ngl 🫢

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

two booleans, both already enabled, both living their best lives. periodt 🌈


🧚 MANAGED FILES 🧚

the SELinux process type podsleuth_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. and hey β€” the process's UID still needs to have DAC permissions. SELinux isn't doing all the work for you, bestie πŸ’€

  • podsleuth_cache_t
/var/cache/podsleuth(/.*)?
  • podsleuth_tmp_t β€” no paths listed, she's mysterious like that πŸ™ˆ
  • podsleuth_tmpfs_t β€” also no paths, also mysterious

🌟 FILE CONTEXTS 🌟

SELinux requires files to have an extended attribute to define the file type. like a little name tag but for files 🏷️

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

🌸 STANDARD FILE CONTEXT 🌸

SELinux defines the file context types for the podsleuth. 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 podsleuth_exec_t '/srv/podsleuth/content(/.*)?'
restorecon -R -v /srv/mypodsleuth_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise 🌸

the following file types are defined for podsleuth:

podsleuth_cache_t

  • Set files with the podsleuth_cache_t type, if you want to store the files under the /var/cache directory.

podsleuth_exec_t

  • Set files with the podsleuth_exec_t type, if you want to transition an executable to the podsleuth_t domain.

paths:

/usr/bin/podsleuth, /usr/libexec/hal-podsleuth

podsleuth_tmp_t

  • Set files with the podsleuth_tmp_t type, if you want to store podsleuth temporary files in the /tmp directories.

podsleuth_tmpfs_t

  • Set files with the podsleuth_tmpfs_t type, if you want to store podsleuth files on a tmpfs file system.
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. temporary vs permanent β€” know the difference, iykyk πŸ’…

πŸ’œ 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 the mouse girlies πŸ–±οΈβœ¨

🫢 AUTHOR 🫢

this manual page was auto-generated using sepolicy manpage. a bot wrote this. a bot ate and left no crumbs, honestly πŸ€–πŸ’…


πŸ”₯ SEE ALSO πŸ”₯

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

go read those too, bestie, you're already here and you're doing amazing πŸ’–


and that's the whole page, fr fr β€” brought to you by podsleuth, dated 26-10-06, living in section podsleuth_selinux(8). slay, go label some files πŸŽ€βœ¨

πŸ“¦ where this page comes from