spamd_update_selinux(8)

spamd_update_selinux 💖✨

okay so bestie, gather round, because we're about to get into the SELinux of it all. this is the manual page for spamd_update_selinux — the Security Enhanced Linux Policy for the spamd_update processes. yes, it's giving security, it's giving mandatory access control, and honestly? it kind of ate. let's go 🎀

---

✨ DESCRIPTION ✨

so like, Security-Enhanced Linux secures the spamd_update processes via flexible mandatory access control. no cap, that's the whole vibe. 🔐

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

for example:

ps -eZ | grep spamd_update_t

literally just run that and see what's up 💅

---

🦋 ENTRYPOINTS 🦋

the spamd_update_t SELinux type can be entered via the spamd_update_exec_t file type.

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

• /usr/share/spamassassin/sa-update.cron
• /usr/bin/sa-update

those are the doors you can walk through to get into this domain, iykyk 🚪✨

---

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system.

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

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

the following process types are defined for spamd_update:

• spamd_update_t

Note: semanage permissive -a spamd_update_t can be used to make the process type spamd_update_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.

so like, permissive mode is chill about letting things through, but it's still gonna snitch to the logs. keep that in mind bestie 😭

---

🌈 BOOLEANS 🌈

SELinux policy is customizable based on least access required. spamd_update policy is extremely flexible and has several booleans that allow you to manipulate the policy and run spamd_update with the tightest access possible. we love a customizable queen 👑

• if you want to allow spamd_update to connect to all ports, you must turn on the spamd_update_can_network boolean. Disabled by default.

setsebool -P spamd_update_can_network 1

• 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 system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.

setsebool -P nis_enabled 1

that's the whole boolean situation, no notes 💅

---

🎀 MANAGED FILES 🎀

the SELinux process type spamd_update_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. note: the process's UID still needs to have DAC permissions. so like, SELinux can say yes but DAC might still say no — know the difference 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

gpg_secret_t

/root/.gnupg(/.+)?
/etc/mail/spamassassin/sa-update-keys(/.*)?
/home/[^/]+/.gnupg(/.+)?

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

root_t

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

spamc_home_t

/root/.pyzor(/.*)?
/root/.razor(/.*)?
/root/.spamd(/.*)?
/root/.spamassassin(/.*)?
/home/[^/]+/.pyzor(/.*)?
/home/[^/]+/.razor(/.*)?
/home/[^/]+/.spamd(/.*)?
/home/[^/]+/.spamassassin(/.*)?

spamd_log_t

/var/log/spamd.log.*
/var/log/mimedefang.*
/var/log/pyzord.log.*
/var/log/sa-update.log.*
/var/log/razor-agent.log.*

spamd_tmp_t

(no paths listed, it's mysterious like that 🙈)

spamd_var_lib_t

/var/lib/razor(/.*)?
/var/lib/pyzord(/.*)?
/var/lib/spamassassin(/.*)?

systemd_passwd_var_run_t

/run/systemd/ask-password(/.*)?
/run/systemd/ask-password-block(/.*)?

that's the whole managed files roster, and honestly it's giving comprehensive ✨

---

🧚 FILE CONTEXTS 🧚

SELinux requires files to have an extended attribute to define the file type.

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the spamd_update, 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. so like, if you want to move things around, you gotta tell SELinux about it first 💅

semanage fcontext -a -t spamd_update_exec_t '/srv/spamd_update/content(/.*)?'
restorecon -R -v /srv/myspamd_update_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise up 🌸

the following file types are defined for spamd_update:

• spamd_update_exec_t — set files with the spamd_update_exec_t type, if you want to transition an executable to the spamd_update_t domain.

paths:

/usr/share/spamassassin/sa-update.cron, /usr/bin/sa-update

• spamd_update_unit_file_t — set files with the spamd_update_unit_file_t type, if you want to treat the files as spamd update unit content.

paths:

/usr/lib/systemd/system/sa-update.timer,
/usr/lib/systemd/system/sa-update.service

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 quick fix, semanage fcontext + restorecon is the forever fix. choose wisely bestie 😭

---

💜 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.

that's the whole toolkit, go off 👑✨

---

🌸 AUTHOR 🌸

This manual page was auto-generated using sepolicy manpage.

(so like, a robot wrote it but i'm here to make it cute 💖)

---

🔥 SEE ALSO 🔥

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

---

okay so that's literally the whole thing bestie 🫶 this page is from spamd_update, version 26-10-06, and yeah, that's the tea. now go forth and configure your SELinux policy like the main character you are 💅✨👑