motion_selinux(8)

💅 motion_selinux(8) — the SELinux policy page for motion, but make it make sense

okay bestie, so this is the manual page for motion_selinux, straight out of the SELinux Policy motion collection. yeah. we're doing this. it's giving "niche but iconic" and honestly? it ate. 🎀

---

✨ NAME ✨

motion_selinux — the Security Enhanced Linux Policy for the motion processes. that's it. that's the whole name section. short queen. 👑

---

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the motion processes via flexible mandatory access control. yes, flexible and mandatory at the same time, the duality of man, we love her. 💅

the motion processes execute with the motion_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier. iykyk.

for example:

ps -eZ | grep motion_t

that's the whole vibe check, bestie. 🦋

---

🚪 ENTRYPOINTS 🚪

so the motion_t SELinux type can be entered via the motion_exec_t file type. that's the door. that's the one way in. 🫶

the default entrypoint paths for the motion_t domain are the following:

/usr/bin/motion

one path. one icon. periodt. ⭐

---

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. that's literally the whole concept, bestie, each process gets a little labeled box and the policy says what's allowed to happen in that box. ✨

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

Policy governs the access confined processes have to files. SELinux motion policy is very flexible allowing users to setup their motion processes in as secure a method as possible. no cap, they really said "flexible" twice on this page and honestly, they're committed to the brand. 💖

the following process types are defined for motion:

motion_t

Note: semanage permissive -a motion_t can be used to make the process type motion_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like... she stops blocking you but she still talks about you in the group chat. 💀

---

🎀 BOOLEANS 🎀

SELinux policy is customizable based on least access required. motion policy is extremely flexible and has several booleans that allow you to manipulate the policy and run motion with the tightest access possible. tightest access is the goal, bestie, we're not out here handing out permissions like candy. 🍓

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

both of these are already on, so like... you can look but don't touch, unless you know what you're doing. 🙈

---

📁 MANAGED FILES 📁

The SELinux process type motion_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. SELinux don't override DAC, that's not her job, she's just the vibe layer on top. 🔥

• cifs_t

(no default paths listed, she's mysterious like that 💜)

• 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

• ecryptfs_t

/home/[^/]+/.Private(/.*)?
/home/[^/]+/.ecryptfs(/.*)?

• fusefs_t

/run/user/[0-9]+/gvfs

• motion_data_t

/var/motion(/.*)?

• motion_log_t

/var/log/motion.log.*

• motion_var_run_t

/run/motion.pid

• nfs_t

(again, no default paths, she's keeping it lowkey 🌈)

• root_t

/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp

• zoneminder_var_lib_t

/var/lib/zoneminder(/.*)?

that's the whole list, bestie, every single one, i didn't skip a single path because that would be a betrayal of the highest order. 🫶

---

🗂️ FILE CONTEXTS 🗂️

SELinux requires files to have an extended attribute to define the file type. yes, files have labels too, everyone's got a label, it's very "everyone's a main character". 👑

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

🌟 STANDARD FILE CONTEXT 🌟

SELinux defines the file context types for the motion, 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. slay, a two-step process, we love a workflow. 💅

semanage fcontext -a -t motion_exec_t '/srv/motion/content(/.*)?'
restorecon -R -v /srv/mymotion_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. yes bestie, regex, she's back, and she's matching multiple files at once. 😭

the following file types are defined for motion:

motion_data_t

• Set files with the motion_data_t type, if you want to treat the files as motion content.

motion_exec_t

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

motion_log_t

• Set files with the motion_log_t type, if you want to treat the data as motion log data, usually stored under the /var/log directory.

motion_unit_file_t

• Set files with the motion_unit_file_t type, if you want to treat the files as motion unit content.

motion_var_run_t

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

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. so like, chcon is the "just for tonight" of labeling and semanage fcontext + restorecon is the "moving in together". 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.

semanage boolean can also be used to manipulate the booleans

system-config-selinux is a GUI tool available to customize SELinux policy settings. yes, there's a GUI, no, i haven't forgotten about the mouse girlies. 🖱️✨

---

🧚 AUTHOR 🧚

This manual page was auto-generated using sepolicy manpage. no human hands touched this prose, which honestly explains a lot. 😭

---

🔗 SEE ALSO 🔗

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

---

okay that's the whole page, bestie, every flag, every path, every boolean, every note. you're officially educated on motion_selinux(8). go forth and label responsibly. 💖

this gem was brought to you by the motion source, dated 26-10-06, living at motion_selinux(8) — mwah, love u, bye! 🦋🌸