sshd_session_selinux(8)

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

πŸ’… sshd_session_selinux(8) β€” the SELinux Policy page for sshd_session, bestie

okay so picture this: it's the sshd_session_selinux(8) manual page, it lives in the SELinux Policy sshd_session section, and it's about to tell you literally everything about how SELinux keeps your sshd session processes on a leash. grab a lil snack, we're going in πŸ“


✨ NAME ✨

sshd_session_selinux β€” the Security Enhanced Linux Policy for the sshd_session processes. that's it, that's the name, no cap πŸ’–


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the sshd_session processes via flexible mandatory access control. yes bestie, mandatory β€” not the vibes-based access control some of us run on 🫢

The sshd_session processes execute with the sshd_session_t SELinux type. wanna check if you've got these processes running? just run the ps command with the -Z qualifier. like this:

ps -eZ | grep sshd_session_t

boom. icon behavior. πŸ”₯


πŸ¦‹ ENTRYPOINTS πŸ¦‹

The sshd_session_t SELinux type can be entered via the sshd_session_exec_t file type. that's the doorway, the main character entrance, the velvet rope πŸ’…

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

/usr/libexec/(open)?ssh/sshd-session

πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system. every process gets a whole identity, honestly kind of iconic of SELinux.

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

ps -Z

Policy governs the access confined processes have to files. the SELinux sshd_session policy is very flexible, allowing users to setup their sshd_session processes in as secure a method as possible. flexible and secure? we love a both/and scenario πŸ’œ

The following process types are defined for sshd_session:

  • sshd_session_t
Note: semanage permissive -a sshd_session_t can be used to make the process type sshd_session_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 still talks about you in the group chat 😭

πŸŽ€ BOOLEANS πŸŽ€

SELinux policy is customizable based on least access required. the sshd_session policy is extremely flexible and has several booleans that allow you to manipulate the policy and run sshd_session with the tightest access possible. little toggles, big energy ✨

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 confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. Enabled by default.

setsebool -P kerberos_enabled 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

If you want to enable polyinstantiated directory support, you must turn on the polyinstantiation_enabled boolean. Disabled by default.

setsebool -P polyinstantiation_enabled 1

If you want to allow ssh logins as sysadm_r:sysadm_t, you must turn on the ssh_sysadm_login boolean. Disabled by default.

setsebool -P ssh_sysadm_login 1

If you want to allow a user to login as an unconfined domain, you must turn on the unconfined_login boolean. Enabled by default.

setsebool -P unconfined_login 1

🧚 MANAGED FILES 🧚

The SELinux process type sshd_session_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. and bestie, don't forget: the processes UID still needs to have DAC permissions. SELinux is not out here doing DAC's homework for it πŸ’€

πŸ’– auth_cache_t

/var/cache/coolkey(/.*)?

πŸ’– auth_home_t

/root/.yubico(/.*)?
/root/.config/Yubico(/.*)?
/root/.google_authenticator
/root/.google_authenticator~
/home/[^/]+/.yubico(/.*)?
/home/[^/]+/.config/Yubico(/.*)?
/home/[^/]+/.google_authenticator
/home/[^/]+/.google_authenticator~

πŸ’– cifs_t

(the original lists no default paths here β€” some file types are just mysterious like that πŸ™ˆ)

πŸ’– ecryptfs_t

/home/[^/]+/.Private(/.*)?
/home/[^/]+/.ecryptfs(/.*)?

πŸ’– faillog_t

/var/log/btmp.*
/run/faillock(/.*)?
/var/log/faillog.*
/var/log/tallylog.*

πŸ’– fusefs_t

/run/user/[0-9]+/gvfs

πŸ’– 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

πŸ’– nfs_t

(again, no default paths listed β€” it's giving "I don't do labels" 😌)

πŸ’– pam_var_run_t

/var/(db|adm)/sudo(/.*)?
/run/sudo(/.*)?
/run/pam_ssh(/.*)?
/run/sepermit(/.*)?
/var/lib/sudo(/.*)?
/run/pam_mount(/.*)?
/run/pam_timestamp(/.*)?

πŸ’– security_t

/selinux

πŸ’– sshd_session_var_run_t

(no default paths listed here either β€” lowkey mysterious, highkey fine πŸ’…)

πŸ’– user_tmp_t

/run/tlog(/.*)?
/run/user/[^/]+
/dev/shm/mono.*
/tmp/.ICE-unix(/.*)?
/tmp/.X11-unix(/.*)?
/dev/shm/pulse-shm.*
/run/user
/tmp/.X0-lock
/tmp/hsperfdata_root
/var/tmp/hsperfdata_root
/home/[^/]+/tmp
/home/[^/]+/.tmp
/run/user/[0-9]+
/tmp/gconfd-[^/]+

πŸ’– var_auth_t

/var/ace(/.*)?
/var/rsa(/.*)?
/var/lib/abl(/.*)?
/var/lib/rsa(/.*)?
/var/lib/pam_ssh(/.*)?
/var/lib/pam_shield(/.*)?
/var/opt/quest/vas/vasd(/.*)?
/var/lib/google-authenticator(/.*)?

πŸ’– wtmpdb_journal_t

/var/lib/wtmpdb/wtmp.db-journal

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. yes, every file has a whole label, it's very main character of them πŸŽ€

You can see the context of a file using the -Z option to ls:

ls -Z

Policy governs the access confined processes have to these files. the SELinux sshd_session policy is very flexible, allowing users to setup their sshd_session processes in as secure a method as possible. (yes we said that already, it's still true, let her cook πŸ’œ)

⭐ STANDARD FILE CONTEXT ⭐

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

semanage fcontext -a -t sshd_session_tmpfs_t
'/srv/sshd_session/content(/.*)?'
restorecon -R -v /srv/mysshd_session_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex bestie, she contains multitudes ✨

The following file types are defined for sshd_session:

  • sshd_session_exec_t β€” Set files with the sshd_session_exec_t type, if you want to transition an executable to the sshd_session_t domain. this is the ✨ portal ✨
  • sshd_session_tmpfs_t β€” Set files with the sshd_session_tmpfs_t type, if you want to store sshd session files on a tmpfs file system. tmpfs said "I can hold her" 🫢
  • sshd_session_var_run_t β€” Set files with the sshd_session_var_run_t type, if you want to store the sshd session files under the /run or /var/run directory. run directory vibes only πŸ’…
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 up 😭

πŸ”₯ 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. a whole graphical interface?? for us?? obsessed 😌✨


🫢 AUTHOR 🫢

This manual page was auto-generated using sepolicy manpage. a bot wrote this and honestly? it ate. πŸ’…


🌟 SEE ALSO 🌟

selinux(8), sshd_session(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8) β€” go read those next, iykyk πŸ¦‹


and that's the whole page bestie!! this was the sshd_session page from 26-10-06, delivered to you by way of sshd_session_selinux(8) β€” auto-generated by sepolicy manpage, read with love, slay, periodt πŸ‘‘πŸ’–

πŸ“¦ where this page comes from