prosody_selinux(8)

📦
version 20250627+git412.dbf877ab7 · 7 versions
, in opensuse-leap 16.0

💅 prosody_selinux(8) — the SELinux glow-up for prosody

okay bestie, so this is prosody_selinux(8), the SELinux Policy page for prosody — yes, the manual is literally called that, and yes it's about keeping prosody's processes on a very short leash. come sit with me, we're gonna get through it together 🫶

✨ NAME ✨

prosody_selinux — Security Enhanced Linux Policy for the prosody processes 💖

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the prosody processes via flexible mandatory access control. that's the whole vibe: prosody doesn't get to just do stuff, it gets to do what policy says it can do. icon behavior honestly ✨

The prosody processes execute with the prosody_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 prosody_t

easy. go look. i'll wait 💅

🦋 ENTRYPOINTS 🦋

The prosody_t SELinux type can be entered via the prosody_exec_t file type. that's the doorway, and only the exec file types listed here unlock it.

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

/usr/bin/prosody, /usr/bin/prosodyctl

two little doors. that's it. no cap 🔥

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. yes, every lil process gets a type. main character energy per process, truly.

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

Policy governs the access confined processes have to files. SELinux prosody policy is very flexible allowing users to setup their prosody processes in as secure a method as possible.

The following process types are defined for prosody:

  • prosody_t
Note: semanage permissive -a prosody_t can be used to make the process type prosody_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so it's like "you can do whatever, but i'm still writing it down in my notes" 😭 use responsibly.

🎀 BOOLEANS 🎀

SELinux policy is customizable based on least access required. prosody policy is extremely flexible and has several booleans that allow you to manipulate the policy and run prosody with the tightest access possible. tune them like your playlist, but like… carefully 🔥

  • prosody_bind_http_port — if you want to permit to prosody to bind apache port. Need to be activated to use BOSH. Disabled by default. turn it on with:
setsebool -P prosody_bind_http_port 1
  • daemons_dontaudit_scheduling — if you want to dontaudit all daemons scheduling requests (setsched, sys_nice). Enabled by default. turn it on with:
setsebool -P daemons_dontaudit_scheduling 1
  • fips_mode — if you want to allow all domains to execute in fips_mode. Enabled by default. turn it on with:
setsebool -P fips_mode 1
  • nis_enabled — if you want to allow system to run with NIS. Disabled by default. turn it on with:
setsebool -P nis_enabled 1

🌈 PORT TYPES 🌈

SELinux defines port types to represent TCP and UDP ports. yes, ports get types too, everyone's got a label at this point honestly.

You can see the types associated with a port by using the following command:

semanage port -l

Policy governs the access confined processes have to these ports. SELinux prosody policy is very flexible allowing users to setup their prosody processes in as secure a method as possible.

The following port types are defined for prosody:

  • prosody_port_t

Default Defined Ports:

tcp 5280-5281

those two. guard them 🫶

🍓 MANAGED FILES 🍓

The SELinux process type prosody_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 isn't out here overriding your normal perms, bestie, it stacks on top 💜

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

krb5_host_rcache_t

/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0

prosody_log_t

/var/log/prosody(/.*)?

prosody_tmp_t

(no default paths listed — it's giving "you know where /tmp is" 💀)

prosody_var_lib_t

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

prosody_var_run_t

/run/prosody(/.*)?

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. every file's got a little label on it, like a name tag at a party 🎀

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the prosody, 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. like this:

semanage fcontext -a -t prosody_exec_t '/srv/prosody/content(/.*)?'
restorecon -R -v /srv/myprosody_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise ✨

The following file types are defined for prosody:

  • prosody_exec_t — Set files with the prosody_exec_t type, if you want to transition an executable to the prosody_t domain.

Paths:

/usr/bin/prosody, /usr/bin/prosodyctl
  • prosody_log_t — Set files with the prosody_log_t type, if you want to treat the data as prosody log data, usually stored under the /var/log directory.
  • prosody_tmp_t — Set files with the prosody_tmp_t type, if you want to store prosody temporary files in the /tmp directories.
  • prosody_unit_file_t — Set files with the prosody_unit_file_t type, if you want to treat the files as prosody unit content.
  • prosody_var_lib_t — Set files with the prosody_var_lib_t type, if you want to store the prosody files under the /var/lib directory.
  • prosody_var_run_t — Set files with the prosody_var_run_t type, if you want to store the prosody 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. temporary vs permanent is literally the whole plot here, don't mix them up 😭

🧚 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 port can also be used to manipulate the port definitions.
  • semanage boolean can also be used to manipulate the booleans.
  • system-config-selinux is a GUI tool available to customize SELinux policy settings. a whole GUI, for when you're feeling ✨ clicky ✨

🙈 AUTHOR 🙈

This manual page was auto-generated using sepolicy manpage. no human hand-wrote this one, it manifested 🫶

🌟 SEE ALSO 🌟

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

and that's the whole page, bestie!! 💖✨ this gem was brought to you by prosody, dated 26-10-06, and it goes by the manual name prosody_selinux(8) — slay, goodbye, go label your files 💅🎀

📦 where this page comes from