apcupsd_selinux(8)

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

πŸ’… apcupsd_selinux(8) β€” the SELinux glow-up for apcupsd

Okay bestie, this is the apcupsd_selinux(8) page, and it's genuinely so much more chill than it sounds. It's literally just the SELinux policy that wraps around your apcupsd processes, and I'm gonna walk you through every single flag and file type like we're on FaceTime. No cap, nothing skipped. 🫢


✨ NAME ✨

apcupsd_selinux β€” the Security Enhanced Linux Policy for the apcupsd processes. That's the whole vibe. πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

Security-Enhanced Linux secures the apcupsd processes via flexible mandatory access control. Yes, flexible and mandatory β€” she contains multitudes. πŸ’…

The apcupsd processes execute with the apcupsd_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 apcupsd_t

That's it, that's the vibe check. ⭐


πŸŽ€ ENTRYPOINTS πŸŽ€

The apcupsd_t SELinux type can be entered via the apcupsd_exec_t file type. Like, that's the door. πŸšͺ

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

/usr/bin/apcupsd

🌸 PROCESS TYPES 🌸

SELinux defines process types (domains) for each process running on the system. Every process gets its own little main character era.

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

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

The following process types are defined for apcupsd:

  • apcupsd_t
  • apcupsd_cgi_script_t
Note: semanage permissive -a apcupsd_t can be used to make the process type apcupsd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, she's off the hook but she's still being watched. πŸ‘€

🧚 BOOLEANS 🧚

SELinux policy is customizable based on least access required. apcupsd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run apcupsd with the tightest access possible. Lowkey the most customizable bestie in the game.

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

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

🌈 PORT TYPES 🌈

SELinux defines port types to represent TCP and UDP ports. Ports have types now, we love to see it.

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

The following port types are defined for apcupsd:

  • apcupsd_port_t

Default Defined Ports:

tcp 3551
udp 3551

Both protocols, same number, iconic behavior. πŸ”₯


πŸ’œ MANAGED FILES πŸ’œ

The SELinux process type apcupsd_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 doing DAC's job for it, fr fr.

apcupsd_lock_t

/run/lock/LCK..
/run/lock/subsys/apcupsd

apcupsd_log_t

/var/log/apcupsd.events.*
/var/log/apcupsd.status.*

apcupsd_power_t

/etc/apcupsd/powerfail

apcupsd_tmp_t

(no default paths listed β€” she's a mystery, and honestly? respect.) πŸ™ˆ

apcupsd_var_run_t

/run/apcupsd.pid

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

initrc_var_run_t

/run/sysconfig(/.*)?
/run/utmp
/run/keymap
/run/numlock-on
/run/setleds-on
/run/runlevel.dir
/run/setmixer_flag
/run/bootsplashctl

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

systemd_passwd_var_run_t

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

πŸ“ FILE CONTEXTS πŸ“

SELinux requires files to have an extended attribute to define the file type. Yes, files have vibes too, and the vibe is stored in an xattr. ✨

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the apcupsd. If you wanted to store files with these types in 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 apcupsd_exec_t '/srv/apcupsd/content(/.*)?'
restorecon -R -v /srv/myapcupsd_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex queen behavior, honestly. πŸ‘‘

The following file types are defined for apcupsd:

apcupsd_cgi_content_t

  • Set files with the apcupsd_cgi_content_t type, if you want to treat the files as apcupsd cgi content.

apcupsd_cgi_htaccess_t

  • Set files with the apcupsd_cgi_htaccess_t type, if you want to treat the file as a apcupsd cgi access file.

apcupsd_cgi_ra_content_t

  • Set files with the apcupsd_cgi_ra_content_t type, if you want to treat the files as apcupsd cgi read/append content.

apcupsd_cgi_rw_content_t

  • Set files with the apcupsd_cgi_rw_content_t type, if you want to treat the files as apcupsd cgi read/write content.

apcupsd_cgi_script_exec_t

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

Paths:

/var/www/cgi-bin/apcgui(/.*)?, /var/www/apcupsd/multimon.cgi,
/var/www/apcupsd/upsimage.cgi, /var/www/apcupsd/upsstats.cgi,
/var/www/apcupsd/upsfstats.cgi

apcupsd_exec_t

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

apcupsd_initrc_exec_t

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

apcupsd_lock_t

  • Set files with the apcupsd_lock_t type, if you want to treat the files as apcupsd lock data, stored under the /var/lock directory.

Paths:

/run/lock/LCK.., /run/lock/subsys/apcupsd

apcupsd_log_t

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

Paths:

/var/log/apcupsd.events.*, /var/log/apcupsd.status.*

apcupsd_power_t

  • Set files with the apcupsd_power_t type, if you want to treat the files as apcupsd power data.

apcupsd_tmp_t

  • Set files with the apcupsd_tmp_t type, if you want to store apcupsd temporary files in the /tmp directories.

apcupsd_unit_file_t

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

apcupsd_var_run_t

  • Set files with the apcupsd_var_run_t type, if you want to store the apcupsd 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, bestie β€” know the difference. πŸ’€

πŸ’– 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. For the besties who prefer a mouse. πŸ–±οΈ

🌟 AUTHOR 🌟

This manual page was auto-generated using sepolicy manpage. A robot wrote it and I gave it a personality, that's the whole pipeline. πŸ€–πŸ’…


πŸ‘‘ SEE ALSO πŸ‘‘

selinux(8), apcupsd(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), apcupsd_cgi_script_selinux(8)


And that's the whole page, bestie β€” you ate that. 🌈

Signing off with the cute little footer energy: this was apcupsd, dated 26-10-06, page apcupsd_selinux(8). Go forth and label responsibly. πŸŽ€πŸ’–πŸ¦‹

πŸ“¦ where this page comes from