openfortivpn_selinux(8)

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

πŸ’– openfortivpn_selinux β€” the SELinux glow-up for your openfortivpn processes πŸ’–

okay bestie, so this is the openfortivpn_selinux(8) page β€” like, the SELinux policy page for openfortivpn, straight out of the SELinux Policy openfortivpn collection. grab a lil snack, we're going in πŸ“


✨ NAME ✨

openfortivpn_selinux β€” Security Enhanced Linux Policy for the openfortivpn processes. that's the whole vibe. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

Security-Enhanced Linux secures the openfortivpn processes via flexible mandatory access control. yes, "mandatory" β€” SELinux does not ask, it tells. main character energy fr fr πŸ‘‘

The openfortivpn processes execute with the openfortivpn_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 openfortivpn_t

go ahead, run it, i'll wait 🫢


🌸 ENTRYPOINTS 🌸

The openfortivpn_t SELinux type can be entered via the openfortivpn_exec_t file type.

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

/usr/libexec/nm-fortisslvpn-.*, /usr/bin/openfortivpn

those are the doors, that's how you get in πŸšͺ✨


🧚 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 openfortivpn policy is very flexible β€” it literally lets users setup their openfortivpn processes in as secure a method as possible. iconic behavior honestly.

The following process types are defined for openfortivpn:

openfortivpn_t

Note: semanage permissive -a openfortivpn_t can be used to make the process type openfortivpn_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like… it stops yelling "no" but it still writes it all down in its diary πŸ““πŸ’€

πŸŽ€ BOOLEANS πŸŽ€

SELinux policy is customizable based on least access required. openfortivpn policy is extremely flexible and has several booleans that allow you to manipulate the policy and run openfortivpn with the tightest access possible.

If you want to determine whether openfortivpn can connect to the TCP network, you must turn on the openfortivpn_can_network_connect boolean. Enabled by default.

setsebool -P openfortivpn_can_network_connect 1

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

If you want to support ecryptfs home directories, you must turn on the use_ecryptfs_home_dirs boolean. Disabled by default.

setsebool -P use_ecryptfs_home_dirs 1

see how it's giving "customize me"? the -P is doing the heavy lifting so your choices actually stick around after a reboot πŸ”₯


πŸ’œ MANAGED FILES πŸ’œ

The SELinux process type openfortivpn_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.

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

openfortivpn_var_lib_t

/var/lib/NetworkManager-fortisslvpn(/.*)?

root_t

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

that's a whole lot of paths and like… yeah. that's the list. no skips, no cuts, we respect the lore πŸ“œβœ¨


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

Policy governs the access confined processes have to these files. SELinux openfortivpn policy is very flexible β€” again, allowing users to setup their openfortivpn processes in as secure a method as possible.

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the openfortivpn, 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 openfortivpn_exec_t '/srv/openfortivpn/content(/.*)?'
restorecon -R -v /srv/myopenfortivpn_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise πŸ™ˆ

The following file types are defined for openfortivpn:

openfortivpn_exec_t

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

Paths:

/usr/libexec/nm-fortisslvpn-.*, /usr/bin/openfortivpn

openfortivpn_var_lib_t

  • Set files with the openfortivpn_var_lib_t type, if you want to store the openfortivpn files under the /var/lib 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, bestie β€” know the difference or your labels will ghost 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.

semanage really said "i contain multitudes" πŸ’…βœ¨


πŸ‘‘ AUTHOR πŸ‘‘

This manual page was auto-generated using sepolicy manpage.

(so no, a human didn't hand-write this one β€” the robots ate and left no crumbs πŸ€–πŸ”₯)


πŸ’– SEE ALSO πŸ’–

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

go read those next, i believe in you 🌟


and that's the whole page, bestie! this one's dated 26-10-06, it's the openfortivpn manual page, and it lives at openfortivpn_selinux(8) β€” so like, same time next week for the reread? k bye ily πŸŽ€πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from