fingerd_selinux(8)

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

💅 fingerd_selinux — the SELinux glow-up for your fingerd processes 💅

Okay bestie, so this is the manual page for fingerd_selinux, and it's literally all about keeping your fingerd daemon safe and slaying securely under SELinux. Fr fr, if you've ever wondered how to lock down fingerd with mandatory access control, this is your moment. Let's get into it. 🎀

✨ NAME ✨

fingerd_selinux — Security Enhanced Linux Policy for the fingerd processes. No cap, that's the whole vibe. 🦋

🌸 DESCRIPTION 🌸

So Security-Enhanced Linux secures the fingerd processes via flexible mandatory access control. It's giving very much "protective bestie energy." 💖

The fingerd processes run with the fingerd_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. Periodt.

For example:

ps -eZ | grep fingerd_t

That's it. That's the check. Slay. ✨

🎀 ENTRYPOINTS 🎀

The fingerd_t SELinux type can be entered via the fingerd_exec_t file type. That's the doorway, bestie. 👑

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

/usr/bin/[cef]fingerd, /usr/bin/in.(x)?fingerd,
/etc/cron.weekly/(c)?fingerd

Iconic. Note those exactly, okay? 💅

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. It's basically labeling everyone at the party so the bouncer knows who's who. 🧚

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

Policy governs the access confined processes have to files. SELinux fingerd policy is very flexible, allowing users to setup their fingerd processes in as secure a method as possible. Highkey obsessed with that flexibility. 🌈

The following process types are defined for fingerd:

  • fingerd_t
Note: semanage permissive -a fingerd_t can be used to make the process type fingerd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So it's like, still watching you, but not blocking. Kinda sus but useful for debugging. 👀

🔥 BOOLEANS 🔥

SELinux policy is customizable based on least access required. The fingerd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run fingerd with the tightest access possible. We love a configurable queen. 💜

  • 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

That's the whole boolean roster. Don't skip any, bestie. 🍓

⭐ PORT TYPES ⭐

SELinux defines port types to represent TCP and UDP ports. It's giving very organized energy. 🎀

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 fingerd policy is very flexible, allowing users to setup their fingerd processes in as secure a method as possible. Again with the flexibility — we love to see it. 💖

The following port types are defined for fingerd:

  • fingerd_port_t

Default Defined Ports:

tcp 79

Port 79 is the fingerd main character. 💅

🦋 MANAGED FILES 🦋

The SELinux process type fingerd_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. Don't forget that part, bestie — SELinux isn't doing the whole job alone. 😭

  • 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
  • fingerd_var_run_t
/run/*.fingerd.pid
  • 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

Yep, that's a lot of paths, but every single one matters. Don't @ me. 🙈

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. It's basically the file's aesthetic but for security. ✨

You can see the context of a file using the -Z option to ls. Lowkey a lifesaver.

Policy governs the access confined processes have to these files. SELinux fingerd policy is very flexible, allowing users to setup their fingerd processes in as secure a method as possible. (Yes, it says this again. It's that important. 💅)

💖 STANDARD FILE CONTEXT 💖

SELinux defines the file context types for the fingerd. 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. Bestie, this is the glow-up for your file labels. 🎀

semanage fcontext -a -t fingerd_exec_t '/srv/fingerd/content(/.*)?'
restorecon -R -v /srv/myfingerd_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. So it's like, pattern matching but make it security. 🦋

The following file types are defined for fingerd:

  • fingerd_etc_t — Set files with the fingerd_etc_t type if you want to store fingerd files in the /etc directories.
  • fingerd_exec_t — Set files with the fingerd_exec_t type if you want to transition an executable to the fingerd_t domain.

Paths:

/usr/bin/[cef]fingerd, /usr/bin/in.(x)?fingerd,
/etc/cron.weekly/(c)?fingerd
  • fingerd_log_t — Set files with the fingerd_log_t type if you want to treat the data as fingerd log data, usually stored under the /var/log directory.
  • fingerd_var_run_t — Set files with the fingerd_var_run_t type if you want to store the fingerd 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 quick fix, semanage fcontext is the permanent era. 💜

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

All the tools you need to be the main character of your own SELinux setup. 🔥

🌟 AUTHOR 🌟

This manual page was auto-generated using sepolicy manpage. Auto-generated and still iconic. 💅

🎀 SEE ALSO 🎀

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

Go read those too if you want the full lore. Iykyk. 💖

Okay bestie, that's the whole page. This was fingerd_selinux(8) from the fingerd package, dated 26-10-06, version fingerd_selinux(8). Slay securely, and remember: SELinux is your friend, not your opp. Periodt. 💅✨🦋

📦 where this page comes from