user_ssh_...t_selinux(8)

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

πŸ’… NAME πŸ’…

okay so bestie, welcome to user_ssh_...t_selinux(8) β€” the manual name is doing a little cryptic slay, but the NAME is user_ssh_agent_selinux: Security Enhanced Linux Policy for the user_ssh_agent processes πŸ’–. The header is also out here saying it's SELinux Policy for user_ssh_agent, so yeah β€” same main character energy ✨.

✨ DESCRIPTION ✨

Security-Enhanced Linux secures the user_ssh_agent processes via flexible mandatory access control. It's giving secure, flexible, mandatory-access-control realness πŸ›‘οΈβœ¨.

The user_ssh_agent processes execute with the user_ssh_agent_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier, like this:

ps -eZ | grep user_ssh_agent_t

No cap, that grep is the vibe check 🫢.

πŸšͺ ENTRYPOINTS πŸšͺ

The user_ssh_agent_t SELinux type can be entered via the ssh_agent_exec_t file type. That's the doorway, periodt πŸšͺ✨.

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

/usr/libexec/(open)?ssh/ssh-pkcs11-helper, /usr/bin/ssh-agent

🧠 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 πŸ‘€.

Policy governs the access confined processes have to files. SELinux user_ssh_agent policy is very flexible allowing users to setup their user_ssh_agent processes in as secure a method as possible. Tightest access possible = bestie behavior πŸ’….

The following process types are defined for user_ssh_agent:

user_ssh_agent_t
Note: semanage permissive -a user_ssh_agent_t can be used to make the process type user_ssh_agent_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. 🚨

πŸŽ€ BOOLEANS πŸŽ€

SELinux policy is customizable based on least access required. user_ssh_agent policy is extremely flexible and has several booleans that allow you to manipulate the policy and run user_ssh_agent with the tightest access possible. Little toggles, big security 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 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 user_ssh_agent_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. πŸ”

cache_home_t

/root/.cache(/.*)?
/home/[^/]+/.nv(/.*)?
/home/[^/]+/.cache(/.*)?

cifs_t β€” file type listed, no default paths listed.

ecryptfs_t

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

fusefs_t

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

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 β€” file type listed, no default paths listed.

πŸ› οΈ 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.

πŸ‘‘ AUTHOR πŸ‘‘

This manual page was auto-generated using sepolicy manpage . Auto-generated icon behavior πŸ‘‘.

πŸ”— SEE ALSO πŸ”—

selinux(8), user_ssh_agent(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8).


and that's the page, bestie 🫢. Cute sign-off time: source/version tag user_ssh_agent, date 26-10-06, and manual name user_ssh_...t_selinux(8) β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from