sshd_keygen_selinux(8)

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

πŸ’… sshd_keygen_selinux(8) β€” the glow-up edition πŸŽ€

okay so bestie, you've stumbled into sshd_keygen_selinux(8), the SELinux policy page for the sshd_keygen processes. it's giving "niche but important" and honestly? we're obsessed. let's get into it ✨


🌸 NAME 🌸

sshd_keygen_selinux β€” the Security Enhanced Linux Policy for the sshd_keygen processes. literally that's the whole vibe. 🫢


✨ DESCRIPTION ✨

Security-Enhanced Linux secures the sshd_keygen processes via flexible mandatory access control. no cap, that's the whole point β€” SELinux keeps these processes on a leash so they can't go off and do main-character chaos. πŸ‘‘

the sshd_keygen processes execute with the sshd_keygen_t SELinux type. wanna check if you've got these processes running rn? just run the ps command with the -Z qualifier. easy.

for example:

ps -eZ | grep sshd_keygen_t

that's it. that's the vibe check. πŸ’…


πŸ¦‹ ENTRYPOINTS πŸ¦‹

the sshd_keygen_t SELinux type can be entered via the sshd_keygen_exec_t file type. think of it as the door you gotta walk through to get into the domain. πŸšͺ

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

/usr/libexec/(open)?ssh/sshd-keygen, /usr/bin/sshd-keygen,
/usr/bin/sshd-gen-keys-start

πŸ’œ PROCESS TYPES πŸ’œ

SELinux defines process types (domains) for each process running on the system. yes, every process gets its own little designated lane. iconic.

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

policy governs the access confined processes have to files. the SELinux sshd_keygen policy is very flexible, allowing users to setup their sshd_keygen processes in as secure a method as possible. tight security but make it customizable πŸ’–

the following process types are defined for sshd_keygen:

  • sshd_keygen_t
Note: semanage permissive -a sshd_keygen_t can be used to make the process type sshd_keygen_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like… it won't block you, but it's still gonna talk about you behind your back. πŸ™ˆ

πŸ“ BOOLEANS πŸ“

SELinux policy is customizable based on least access required. the sshd_keygen policy is extremely flexible and has several booleans that allow you to manipulate the policy and run sshd_keygen 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

🌈 MANAGED FILES 🌈

the SELinux process type sshd_keygen_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 DAC, bestie, they're a team. 🀝

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

sshd_key_t

/etc/ssh/ssh_host.*_key
/etc/ssh/ssh_host.*_key.pub
/etc/ssh/primes

🧚 FILE CONTEXTS 🧚

SELinux requires files to have an extended attribute to define the file type. it's like a little name tag but for files, and honestly? so valid of them. 🏷️

you can see the context of a file using the -Z option to ls.

policy governs the access confined processes have to these files. the SELinux sshd_keygen policy is very flexible, allowing users to setup their sshd_keygen processes in as secure a method as possible. yes she's flexible, yes she's secure, we stan. πŸ’…

✨ STANDARD FILE CONTEXT ✨

SELinux defines the file context types for the sshd_keygen. 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.

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

the following file types are defined for sshd_keygen:

sshd_keygen_exec_t

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

Paths:

/usr/libexec/(open)?ssh/sshd-keygen, /usr/bin/sshd-keygen,
/usr/bin/sshd-gen-keys-start

sshd_keygen_unit_file_t

  • Set files with the sshd_keygen_unit_file_t type, if you want to treat the files as sshd keygen unit content.
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 temporary tattoo, semanage fcontext + restorecon is the real ink. 🌸

πŸ’€ COMMANDS πŸ’€

semange fcontext can also be used to manipulate default file context mappings.

semange permissive can also be used to manipulate whether or not a process type is permissive.

semange module can also be used to enable/disable/install/remove policy modules.

semange boolean can also be used to manipulate the booleans.

system-config-selinux is a GUI tool available to customize SELinux policy settings. yes bestie, a whole GUI, for when you simply cannot with the terminal today. πŸ–±οΈβœ¨


πŸ‘‘ AUTHOR πŸ‘‘

this manual page was auto-generated using sepolicy manpage. a bot wrote this and honestly it ate. πŸ”₯


🌟 SEE ALSO 🌟

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

go read those too, iykyk πŸ’–


and that's the whole page, bestie! this one's from sshd_keygen, dated 26-10-06, living in sshd_keygen_selinux(8) β€” now go forth and label responsibly πŸŽ€βœ¨πŸ’œ

πŸ“¦ where this page comes from