afs_selinux(8)

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

πŸ’… afs_selinux(8) β€” bestie's guide to the afs SELinux policy πŸŽ€

okay so this is the afs_selinux(8) page, and it's literally all about the Security Enhanced Linux Policy for the afs processes. it's giving "niche but iconic" and honestly? we love her for it. let's get into it 🫢


✨ NAME ✨

afs_selinux β€” Security Enhanced Linux Policy for the afs processes. that's the whole vibe.


🌸 DESCRIPTION 🌸

so bestie, Security-Enhanced Linux secures the afs processes via flexible mandatory access control. yes, mandatory. she's not asking, she's telling πŸ’…

the afs processes execute with the afs_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 afs_t

see? easy. go check your vibes πŸ”


πŸšͺ ENTRYPOINTS πŸšͺ

the afs_t SELinux type can be entered via the afs_exec_t file type. that's the doorway, the main character entrance, the "you may enter" of it all ✨

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

/usr/bin/afsd, /usr/vice/etc/afsd

πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system. one for everybody, no sharing, we stan a dedicated domain πŸ’–

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

policy governs the access confined processes have to files. SELinux afs policy is very flexible, allowing users to setup their afs processes in as secure a method as possible. flexible and secure? she ate πŸ”₯

the following process types are defined for afs:

afs_t, afs_bosserver_t, afs_fsserver_t, afs_kaserver_t, afs_ptserver_t, afs_vlserver_t

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

so like, permissive means she's not blocking you, but she IS still writing it down in her notes. the AVC messages are the receipts, fr fr 😭


🎚️ BOOLEANS 🎚️

SELinux policy is customizable based on least access required. afs policy is extremely flexible and has several booleans that allow you to manipulate the policy and run afs with the tightest access possible. tightest access possible = the most locked-down slay πŸ’…

daemons_dontaudit_scheduling β€” 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

fips_mode β€” 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

nscd_use_shm β€” if you want to allow confined applications to use nscd shared memory, you must turn on the nscd_use_shm boolean. enabled by default.

setsebool -P nscd_use_shm 1

all three come enabled out of the box, which is honestly thoughtful of her πŸŽ€


πŸ”Œ PORT TYPES πŸ”Œ

SELinux defines port types to represent TCP and UDP ports. ports are literally the doorways of the network world, iykyk 🌈

you can see the types associated with a port by using the following command:

semanage port -l

policy governs the access confined processes have to these ports. SELinux afs policy is very flexible, allowing users to setup their afs processes in as secure a method as possible. (yes she said it again, she means it πŸ’œ)

the following port types are defined for afs:

afs3_callback_port_t

default defined ports:

tcp 7001
udp 7001

afs_bos_port_t

default defined ports:

udp 7007

afs_fs_port_t

default defined ports:

tcp 2040
udp 7000,7005

afs_ka_port_t

default defined ports:

udp 7004

afs_pt_port_t

default defined ports:

tcp 7002
udp 7002

afs_vl_port_t

default defined ports:

udp 7003

look at all those little numbered doors πŸšͺ✨


πŸ“ MANAGED FILES πŸ“

the SELinux process type afs_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. note: the process's UID still needs to have DAC permissions. SELinux said "you may", DAC said "ma'am, who are you?" β€” both have to agree 😭

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

root_t

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

unlabeled_t

that's it. no paths listed. she's a mystery, she's unlabeled, she's a vibe πŸ’€


🏷️ FILE CONTEXTS 🏷️

SELinux requires files to have an extended attribute to define the file type. yes, files have labels now. everyone's got a name tag at this party πŸŽ€

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 afs policy is very flexible, allowing users to setup their afs processes in as secure a method as possible. (third time's the charm, she's consistent πŸ‘‘)

🌟 STANDARD FILE CONTEXT 🌟

SELinux defines the file context types for the afs, so if you wanted to store files with these types in 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 afs_exec_t '/srv/afs/content(/.*)?'
restorecon -R -v /srv/myafs_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies, rise 🌸

the following file types are defined for afs:

afs_bosserver_exec_t

  • set files with the afs_bosserver_exec_t type if you want to transition an executable to the afs_bosserver_t domain.

paths:

/usr/bin/bosserver, /usr/afs/bin/bosserver

afs_cache_t

  • set files with the afs_cache_t type if you want to store the files under the /var/cache directory.

paths:

/var/cache/(open)?afs(/.*)?, /usr/vice/cache(/.*)?

afs_config_t

  • set files with the afs_config_t type if you want to treat the files as afs configuration data, usually stored under the /etc directory.

paths:

/etc/(open)?afs(/.*)?, /usr/afs/etc(/.*)?, /usr/afs/local(/.*)?

afs_dbdir_t

  • set files with the afs_dbdir_t type if you want to treat the files as afs dbdir data.

afs_exec_t

  • set files with the afs_exec_t type if you want to transition an executable to the afs_t domain.

paths:

/usr/bin/afsd, /usr/vice/etc/afsd

afs_files_t

  • set files with the afs_files_t type if you want to treat the files as afs content.

paths:

/usr/afs(/.*)?, /vicepa, /vicepb, /vicepc

afs_fsserver_exec_t

  • set files with the afs_fsserver_exec_t type if you want to transition an executable to the afs_fsserver_t domain.

paths:

/usr/afs/bin/salvager, /usr/afs/bin/volserver,
/usr/afs/bin/dasalvager, /usr/afs/bin/fileserver,
/usr/afs/bin/davolserver, /usr/afs/bin/dafileserver,
/usr/afs/bin/salvageserver, /usr/libexec/openafs/salvager,
/usr/libexec/openafs/volserver, /usr/libexec/openafs/fileserver

afs_initrc_exec_t

  • set files with the afs_initrc_exec_t type if you want to transition an executable to the afs_initrc_t domain.

paths:

/etc/rc.d/init.d/(open)?afs, /etc/rc.d/init.d/openafs-client

afs_ka_db_t

  • set files with the afs_ka_db_t type if you want to treat the files as afs ka database content.

afs_kaserver_exec_t

  • set files with the afs_kaserver_exec_t type if you want to transition an executable to the afs_kaserver_t domain.

paths:

/usr/afs/bin/kaserver, /usr/libexec/openafs/kaserver

afs_logfile_t

  • set files with the afs_logfile_t type if you want to treat the files as afs logfile data.

afs_pt_db_t

  • set files with the afs_pt_db_t type if you want to treat the files as afs pt database content.

afs_ptserver_exec_t

  • set files with the afs_ptserver_exec_t type if you want to transition an executable to the afs_ptserver_t domain.

paths:

/usr/afs/bin/ptserver, /usr/libexec/openafs/ptserver

afs_vl_db_t

  • set files with the afs_vl_db_t type if you want to treat the files as afs vl database content.

afs_vlserver_exec_t

  • set files with the afs_vlserver_exec_t type if you want to transition an executable to the afs_vlserver_t domain.

paths:

/usr/afs/bin/vlserver, /usr/libexec/openafs/vlserver
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 and semanage fcontext + restorecon is the real ink. choose wisely bestie πŸ’…


πŸ› οΈ 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 port can also be used to manipulate the port definitions.

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 GUI, for the girlies who like buttons πŸ–±οΈβœ¨


πŸ’œ AUTHOR πŸ’œ

this manual page was auto-generated using sepolicy manpage. no human author to thank, just a script doing her thing πŸ€–πŸ’–


πŸ”— SEE ALSO πŸ”—

selinux(8), afs(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), afs_bosserver_selinux(8), afs_bosserver_selinux(8), afs_fsserver_selinux(8), afs_fsserver_selinux(8), afs_kaserver_selinux(8), afs_kaserver_selinux(8), afs_ptserver_selinux(8), afs_ptserver_selinux(8), afs_vlserver_selinux(8), afs_vlserver_selinux(8)

(yes, several of those are listed twice β€” that's exactly how the original rolls, and we don't edit the queen's guest list πŸ‘‘)


and that's the whole page! this one comes from the afs manual, dated 26-10-06, in section 8 of the man pages β€” mwah, go forth and label responsibly πŸ¦‹πŸ’–

πŸ“¦ where this page comes from