iiosensor...y_selinux(8)
π iiosensorproxy_selinux β bestie's guide to the SELinux policy
okay so real talk, this is a page from the SELinux Policy iiosensorproxy manual set (iiosensor...y_selinux(8) β the name got a lil truncated in the header, she's doing her best π). Sit down, grab a strawberry drink π, and let's get into it.
β¨ NAME β¨
iiosensorproxy_selinux β the Security Enhanced Linux Policy for the iiosensorproxy processes. that's it, that's the whole name. short, sweet, iconic. π
πΈ DESCRIPTION πΈ
Security-Enhanced Linux secures the iiosensorproxy processes via flexible mandatory access control. yes bestie, mandatory β not "please don't" access control, but "you literally cannot" access control. it's giving strict parent energy and honestly? we stan. π
The iiosensorproxy processes execute with the iiosensorproxy_t SELinux type. no cap, that's their whole vibe. You can check if you have these processes running by executing the ps command with the -Z qualifier.
For example:
ps -eZ | grep iiosensorproxy_t
run that and see who's matching the vibe check. π
π¦ ENTRYPOINTS π¦
The iiosensorproxy_t SELinux type can be entered via the iiosensorproxy_exec_t file type. that's the door, the portal, the main character entrance.
The default entrypoint paths for the iiosensorproxy_t domain are the following:
/usr/libexec/iio-sensor-proxy
one path. one. she's lowkey exclusive and I respect it. β¨
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. yes, every process gets a whole identity β very astrology of it.
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. SELinux iiosensorproxy policy is very flexible, allowing users to setup their iiosensorproxy processes in as secure a method as possible. flexible and secure, the duality of woman. π«Ά
The following process types are defined for iiosensorproxy:
iiosensorproxy_t
Note:semanage permissive -a iiosensorproxy_tcan be used to make the process typeiiosensorproxy_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, she won't block you, but she will leave receipts in the group chat. π
π BOOLEANS π
SELinux policy is customizable based on least access required. iiosensorproxy policy is extremely flexible and has several booleans that allow you to manipulate the policy and run iiosensorproxy with the tightest access possible. tightest access = smallest purse, most exclusive guest list. π
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
two booleans, both enabled by default, both little switches you can flip. we love a manageable situation. ποΈ
π§ MANAGED FILES π§
The SELinux process type iiosensorproxy_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 said "I'll handle the labels" but DAC is still not her business, that's on you. fr fr.
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
sysfs_t
/sys(/.*)?
look at all these paths, she's got range. π
π₯ FILE CONTEXTS π₯
SELinux requires files to have an extended attribute to define the file type. yes, files have metadata that says who they are. main character energy for a file, honestly.
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 iiosensorproxy policy is very flexible, allowing users to setup their iiosensorproxy processes in as secure a method as possible.
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the iiosensorproxy. 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 iiosensorproxy_exec_t
'/srv/iiosensorproxy/content(/.*)?'
restorecon -R -v /srv/myiiosensorproxy_content
(that's the literal command, copy it exact, don't get creative with it bestie π)
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex era, we're living in it. π
The following file types are defined for iiosensorproxy:
iiosensorproxy_exec_t
- Set files with the
iiosensorproxy_exec_ttype, if you want to transition an executable to theiiosensorproxy_tdomain. that's the whole glow-up pipeline: right label β right domain. β¨
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels.
so: chcon = temporary fit, semanage fcontext = permanent makeover, restorecon = actually putting the outfit on. π
π COMMANDS π
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage booleancan also be used to manipulate the booleans.system-config-selinuxis a GUI tool available to customize SELinux policy settings. (a GUI! for the girlies who prefer clicking π±οΈπ)
π AUTHOR π
This manual page was auto-generated using sepolicy manpage. a bot wrote this, and honestly? she ate. π€π
π«Ά SEE ALSO π«Ά
selinux(8), iiosensorproxy(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
go read those next, iykyk. π
anyway bestie, that's the whole page β no notes, no cap. this one came from the iiosensorproxy manual, dated 26-10-06, and it's the iiosensor...y_selinux(8) page (the header truncates the name like that, that's just how she's filed π). mwah, go label something responsibly. π
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms