keyboardd_selinux(8)

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

✨ keyboardd_selinux(8) β€” the manual page bestie πŸ’…

okay so this is the keyboardd_selinux page, and honestly it's giving "SELinux but make it keyboard." no cap, we're gonna get through this together 🫢


🌸 NAME 🌸

keyboardd_selinux β€” Security Enhanced Linux Policy for the keyboardd processes. literally what it says on the tin, bestie.


πŸ’– DESCRIPTION πŸ’–

Security-Enhanced Linux secures the keyboardd processes via flexible mandatory access control. it's giving protective big sister energy fr fr.

The keyboardd processes execute with the keyboardd_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier. vibe check via terminal, iconic.

For example:

ps -eZ | grep keyboardd_t

πŸŽ€ ENTRYPOINTS πŸŽ€

The keyboardd_t SELinux type can be entered via the keyboardd_exec_t file type. that's the doorway, bestie πŸšͺ✨

The default entrypoint paths for the keyboardd_t domain are the following:

/usr/bin/system-setup-keyboard

πŸ¦‹ PROCESS TYPES πŸ¦‹

SELinux defines process types (domains) for each process running on the system. yeah, every single one gets its own little label, main character energy for everyone.

You can see the context of a process using the -Z option to ps. highly recommend, it's a slay.

Policy governs the access confined processes have to files. SELinux keyboardd policy is very flexible allowing users to setup their keyboardd processes in as secure a method as possible. flexible and secure? we love to see it πŸ”₯

The following process types are defined for keyboardd:

keyboardd_t
πŸ’€ Note: semanage permissive -a keyboardd_t can be used to make the process type keyboardd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it's not blocking you but it's still taking notes πŸ“

🌈 BOOLEANS 🌈

SELinux policy is customizable based on least access required. keyboardd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run keyboardd with the tightest access possible. booleans are literally the switches of the SELinux world, obsessed.

If you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. Enabled by default.

setsebool -P daemons_dontaudit_scheduling 1

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

πŸ’œ MANAGED FILES πŸ’œ

The SELinux process type keyboardd_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. yes, DAC is still a thing, SELinux doesn't do everything for you bestie πŸ™ˆ

  • cluster_conf_t
/etc/cluster(/.*)?
  • cluster_var_lib_t
/var/lib/pcsd(/.*)?
/var/lib/cluster(/.*)?
/var/lib/openais(/.*)?
/var/lib/pengine(/.*)?
/var/lib/corosync(/.*)?
/usr/lib/heartbeat(/.*)?
/var/lib/heartbeat(/.*)?
/var/lib/pacemaker(/.*)?
  • cluster_var_run_t
/run/crm(/.*)?
/run/cman_.*
/run/rsctmp(/.*)?
/run/aisexec.*
/run/heartbeat(/.*)?
/run/pcsd-ruby.socket
/run/corosync-qnetd(/.*)?
/run/corosync-qdevice(/.*)?
/run/pcsd.socket
/run/corosync.pid
/run/cpglockd.pid
/run/rgmanager.pid
/run/cluster/rgmanager.sk
  • root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp

🧚 FILE CONTEXTS 🧚

SELinux requires files to have an extended attribute to define the file type. it's like a little name tag for every file, cute tbh 🏷️

You can see the context of a file using the -Z option to ls. go check your faves.

Policy governs the access confined processes have to these files. SELinux keyboardd policy is very flexible allowing users to setup their keyboardd processes in as secure a method as possible. (yes we said this already but it bears repeating, it's that iconic ✨)

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the keyboardd, 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. relabeling era πŸ’…

semanage fcontext -a -t keyboardd_exec_t '/srv/keyboardd/content(/.*)?'
restorecon -R -v /srv/mykeyboardd_content
πŸ’‘ Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise πŸ™Œ

The following file types are defined for keyboardd:

  • keyboardd_exec_t β€” Set files with the keyboardd_exec_t type, if you want to transition an executable to the keyboardd_t domain. this is the glow-up transition bestie, it's giving "before and after" πŸ”₯
⚠️ 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, choose wisely 😭

πŸ”₯ 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. modular slay.
  • semanage boolean can also be used to manipulate the booleans.
  • system-config-selinux is a GUI tool available to customize SELinux policy settings. a GUI?? for the mouse girlies?? we respect it πŸ–±οΈπŸ’–

🫢 AUTHOR 🫢

This manual page was auto-generated using sepolicy manpage. a bot wrote this, and honestly? it ate. no notes. πŸ€–βœ¨


🌟 SEE ALSO 🌟

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


anyway bestie that's the whole page πŸ’• this was keyboardd flavored keyboardd_selinux(8) from the 26-10-06 drop, brought to you by the SELinux policy squad. now go forth and label responsibly, mwah! πŸŽ€πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from