readahead_selinux(8)

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

πŸ’– readahead_selinux β€” the SELinux policy page for readahead, but make it make sense πŸ’–

okay bestie, so this is readahead_selinux(8) from the readahead manual β€” yes, that's the manual name, it's giving "very specific corner of the SELinux universe" and honestly? iconic. sit down, hydrate, let's go 🫢


✨ NAME ✨

readahead_selinux β€” the Security Enhanced Linux Policy for the readahead processes. that's it, that's the whole vibe check 🌸


πŸ¦‹ DESCRIPTION πŸ¦‹

Security-Enhanced Linux secures the readahead processes via flexible mandatory access control. yes, mandatory. no, you can't opt out, that's literally the whole point πŸ’…

The readahead processes execute with the readahead_t SELinux type. wanna check if you've got these processes running on your system? just run the ps command with the -Z qualifier, easy:

ps -eZ | grep readahead_t

boom. now you know. πŸ”


πŸŽ€ ENTRYPOINTS πŸŽ€

The readahead_t SELinux type can be entered via the readahead_exec_t file type. think of it like the VIP door into the readahead domain πŸšͺ✨

The default entrypoint paths for the readahead_t domain are literally these:

/usr/bin/readahead.*, /usr/lib/systemd/systemd-readahead.*

πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system. every process gets a little label, it's giving name tags at a party 🏷️

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

Policy governs the access confined processes have to files. SELinux readahead policy is very flexible, allowing users to setup their readahead processes in as secure a method as possible. maximum security, maximum slay πŸ”

The following process types are defined for readahead:

  • readahead_t
Note: semanage permissive -a readahead_t can be used to make the process type readahead_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like… you're not getting blocked, but bestie, everyone can still see the receipts 😭

πŸ”₯ BOOLEANS πŸ”₯

SELinux policy is customizable based on least access required. readahead policy is extremely flexible and has several booleans that allow you to manipulate the policy and run readahead with the tightest access possible. tighter than your favorite jeans, fr fr πŸ’œ

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

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. no attribute, no entry, that's the rule 🎫

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the readahead β€” so 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. relocation era πŸ’«

semanage fcontext -a -t readahead_exec_t '/srv/readahead/content(/.*)?'
restorecon -R -v /srv/myreadahead_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies stay winning 🧚

The following file types are defined for readahead:

readahead_exec_t

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

Paths:

/usr/bin/readahead.*, /usr/lib/systemd/systemd-readahead.*

readahead_var_lib_t

  • Set files with the readahead_var_lib_t type, if you want to store the readahead files under the /var/lib directory.

readahead_var_run_t

  • Set files with the readahead_var_run_t type, if you want to store the readahead files under the /run or /var/run directory.

Paths:

/run/readahead.*, /run/systemd/readahead(/.*)?,
/dev/.systemd/readahead(/.*)?
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 is literally the plot of every coming-of-age movie 😭

πŸ’… 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 bestie, a GUI, for when the terminal is doing too much πŸ–±οΈβœ¨


πŸ“ AUTHOR πŸ“

This manual page was auto-generated using sepolicy manpage. a bot wrote this and honestly it ate πŸ€–πŸ’–


πŸ’œ SEE ALSO πŸ’œ

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


okay so that's the whole page!! source/version is readahead, dated 26-10-06, and it's all readahead_selinux(8) business β€” go forth and label responsibly, ily, bye πŸŽ€πŸ¦‹πŸ’–

πŸ“¦ where this page comes from