SYSTEMD_SSH_ISSUE_SELINUX(8)

💖 systemd_ssh_issue_selinux — the manual page, but make it make sense 💖

okay so real talk, bestie: this is the systemd_ssh_issue_selinux page from the SELinux Policy manual set (section 8, we love a numbered section ✨). It's all about the SELinux policy for the systemd_ssh_issue processes. Stick with me, it's actually not scary, i promise 🫶

---

✨ NAME ✨

systemd_ssh_issue_selinux — Security Enhanced Linux Policy for the systemd_ssh_issue processes 🎀

---

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the systemd_ssh_issue processes via flexible mandatory access control. like, it's giving strict-but-fair parent energy 💅

The systemd_ssh_issue processes execute with the systemd_ssh_issue_t SELinux type. Wanna check if you've got these processes running? just run the ps command with the -Z qualifier, easy:

ps -eZ | grep systemd_ssh_issue_t

that's it. that's the vibe check 🔍

---

🦋 ENTRYPOINTS 🦋

The systemd_ssh_issue_t SELinux type can be entered via the systemd_ssh_issue_exec_t file type. (yes, entry via exec type, classic transition behavior, iykyk)

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

/usr/lib/systemd/systemd-ssh-issue

one path, one icon, no cap 👑

---

🎀 PROCESS TYPES 🎀

SELinux defines process types (domains) for each process running on the system. so every process gets its own little label, main character energy fr fr ✨

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

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

The following process types are defined for systemd_ssh_issue:

• systemd_ssh_issue_t

Note: semanage permissive -a systemd_ssh_issue_t can be used to make the process type systemd_ssh_issue_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it stops blocking you but it's still gonna gossip about you in the logs 😭💀

---

💜 BOOLEANS 💜

SELinux policy is customizable based on least access required. systemd_ssh_issue policy is extremely flexible and has several booleans that allow you to manipulate the policy and run systemd_ssh_issue with the tightest access possible. tightest access possible = the whole point, bestie 🫶

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 last one is off by default for a reason — only flip it if you actually need NIS, ngl 🙈)

---

🌟 MANAGED FILES 🌟

The SELinux process type systemd_ssh_issue_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 is not out here doing DAC's job for it 💅

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

root_t

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

systemd_ssh_issue_var_run_t

/run/issue.d(/.*)?

---

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. yes, files have vibes too, and their vibe is written 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 systemd_ssh_issue policy is very flexible, allowing users to setup their systemd_ssh_issue processes in as secure a method as possible.

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the systemd_ssh_issue. 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 relabeling but make it intentional ✨

semanage fcontext -a -t systemd_ssh_issue_exec_t
'/srv/systemd_ssh_issue/content(/.*)?'
restorecon -R -v /srv/mysystemd_ssh_issue_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex my beloved 🧚

The following file types are defined for systemd_ssh_issue:

systemd_ssh_issue_exec_t

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

systemd_ssh_issue_var_run_t

• Set files with the systemd_ssh_issue_var_run_t type, if you want to store the systemd ssh issue 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, know the difference bestie, it WILL come back to bite you 😭🔥

---

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

five tools, five little slayers, go off 🫶💅

---

🍓 AUTHOR 🍓

This manual page was auto-generated using sepolicy manpage. yes the robots wrote it, and we're grateful 🙈✨

---

🔥 SEE ALSO 🔥

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

---

and that's the whole page bestie, you ate that 🎀 ok bye ily — this little number is systemd_ssh_issue, dated 26-10-06, from the systemd_...e_selinux(8) manual. mwah 💋💖