local_login_selinux(8)

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

✨ local_login_selinux β€” bestie edition ✨

Okay so real talk, this is the SELinux policy page for the local_login processes, and it's genuinely so important if you care about keeping your system's login flow locked down. Security-Enhanced Linux secures the local_login processes via flexible mandatory access control. Periodt. πŸ’…

🌸 NAME 🌸

local_login_selinux β€” the Security Enhanced Linux Policy for the local_login processes, aka the glow-up your login security deserves.

πŸ¦‹ DESCRIPTION πŸ¦‹

Security-Enhanced Linux secures the local_login processes via flexible mandatory access control. Slay.

The local_login processes execute with the local_login_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 local_login_t

πŸŽ€ ENTRYPOINTS πŸŽ€

The local_login_t SELinux type can be entered via the login_exec_t file type.

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

/usr/bin/login, /usr/kerberos/sbin/login.krb5

πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system.

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

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

The following process types are defined for local_login:

  • local_login_t
Note: semanage permissive -a local_login_t can be used to make the process type local_login_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's chill but not that chill β€” you still get receipts. πŸ‘€

πŸ’œ BOOLEANS πŸ’œ

SELinux policy is customizable based on least access required. local_login policy is extremely flexible and has several booleans that allow you to manipulate the policy and run local_login with the tightest access possible. Tightest access = main character energy, fr fr.

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 logging in and using the system from /dev/console, you must turn on the login_console_enabled boolean. Enabled by default.

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

🌈 MANAGED FILES 🌈

The SELinux process type local_login_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. Don't forget the UID tea, bestie. 🍡

  • 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~
  • faillog_t
/var/log/btmp.*
/run/faillock(/.*)?
/var/log/faillog.*
/var/log/tallylog.*
  • 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
  • local_login_lock_t
  • pam_var_console_t
/run/console(/.*)?
  • 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
  • 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.

You can see the context of a file using the -Z option to ls. Go off, ls -Z.

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

🧚 STANDARD FILE CONTEXT 🧚

SELinux defines the file context types for the local_login, 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 local_login_home_t '/srv/local_login/content(/.*)?'
restorecon -R -v /srv/mylocal_login_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex girlies stay winning. πŸ’…

The following file types are defined for local_login:

  • local_login_home_t
    • Set files with the local_login_home_t type, if you want to store local login files in the users home directory.

Paths:

/root/.hushlogin, /home/[^/]+/.hushlogin
  • local_login_lock_t
    • Set files with the local_login_lock_t type, if you want to treat the files as local login lock data, stored under the /var/lock 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. Don't skip the restorecon step, bestie, I'm begging 😭

πŸ”₯ 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. GUI girlies, this one's for you 🫢

πŸ“ AUTHOR πŸ“

This manual page was auto-generated using sepolicy manpage. Automated and still ate. ✨

πŸ’– SEE ALSO πŸ’–

selinux(8), local_login(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8) β€” go read these too, iykyk.


And that's the whole vibe check, bestie! This page is from the local_login manpage collection, dated 26-10-06, and it's literally all about keeping your local_login processes secure and iconic. Now go forth and setsebool responsibly! πŸŒŸπŸ’œ

πŸ“¦ where this page comes from