ktalkd_selinux(8)

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

πŸ’… ktalkd_selinux(8) β€” the ktalkd SELinux page, but make it make sense

okay so real talk: this is the ktalkd_selinux manual, page (8), straight out of the SELinux Policy ktalkd section of the manual. bestie, it's giving "niche but iconic" β€” let's get into it πŸŽ€


✨ NAME ✨

ktalkd_selinux β€” Security Enhanced Linux Policy for the ktalkd processes 🫢


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the ktalkd processes via flexible mandatory access control. no cap, that's the whole vibe β€” the policy is the bouncer, the processes are the guests πŸ’…

The ktalkd processes execute with the ktalkd_t SELinux type. wanna check if you've got these processes running? run the ps command with the -Z qualifier, like so:

ps -eZ | grep ktalkd_t

literally that simple. go off πŸ”₯


πŸ¦‹ ENTRYPOINTS πŸ¦‹

The ktalkd_t SELinux type can be entered via the ktalkd_exec_t file type.

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

/usr/bin/ktalkd, /usr/bin/in.talkd, /usr/bin/in.ntalkd

those three are the main characters of this story πŸ‘‘


⭐ 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 ktalkd policy is very flexible, allowing users to setup their ktalkd processes in as secure a method as possible. yes, flexible and secure, we contain multitudes πŸ’–

The following process types are defined for ktalkd:

  • ktalkd_t
Note: semanage permissive -a ktalkd_t can be used to make the process type ktalkd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it's not a free pass, the receipts still exist 😭

πŸ“ BOOLEANS πŸ“

SELinux policy is customizable based on least access required. ktalkd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run ktalkd with the tightest access possible. tune it like a playlist 🎧

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

see? three little switches, three little vibes ✨


🌈 PORT TYPES 🌈

SELinux defines port types to represent TCP and UDP ports.

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 ktalkd policy is very flexible, allowing users to setup their ktalkd processes in as secure a method as possible.

The following port types are defined for ktalkd:

  • ktalkd_port_t

Default Defined Ports:

udp 517,518

udp 517 and 518, noted, memorized, immortalized πŸ’€


🧚 MANAGED FILES 🧚

The SELinux process type ktalkd_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 "I'll handle MAC, you handle the rest" πŸ™ˆ

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

ktalkd_tmp_t

(nope, no default paths listed for this one β€” it's a mystery, an enigma, a vibe πŸ¦‹)

root_t

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

that's a lot of paths and honestly? respect for the documentation effort πŸ‘


πŸ’œ 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 ktalkd policy is very flexible, allowing users to setup their ktalkd processes in as secure a method as possible.

πŸŽ€ STANDARD FILE CONTEXT πŸŽ€

SELinux defines the file context types for the ktalkd. 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. it's a two-step, no shortcuts πŸ’…

semanage fcontext -a -t ktalkd_exec_t '/srv/ktalkd/content(/.*)?'
restorecon -R -v /srv/myktalkd_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex said "I contain multitudes" ✨

The following file types are defined for ktalkd:

ktalkd_exec_t

  • Set files with the ktalkd_exec_t type if you want to transition an executable to the ktalkd_t domain.

Paths:

/usr/bin/ktalkd, /usr/bin/in.talkd, /usr/bin/in.ntalkd

ktalkd_log_t

  • Set files with the ktalkd_log_t type if you want to treat the data as ktalkd log data, usually stored under the /var/log directory. πŸ““

ktalkd_tmp_t

  • Set files with the ktalkd_tmp_t type if you want to store ktalkd temporary files in the /tmp directories.

ktalkd_unit_file_t

  • Set files with the ktalkd_unit_file_t type if you want to treat the files as ktalkd unit content.
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 situationship, semanage fcontext is the commitment πŸ˜­πŸ’

πŸ”₯ 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.

six whole commands, all iconic, all yours πŸ‘‘


πŸ‘‘ AUTHOR πŸ‘‘

This manual page was auto-generated using sepolicy manpage. yes, a robot wrote it, and honestly it ate πŸ€–βœ¨


🌸 SEE ALSO 🌸

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


that's the whole page bestie, every single detail preserved, nothing dropped, periodt πŸ’…

ktalkd Β· 26-10-06 Β· ktalkd_selinux(8) β€” mwah, go be secure out there πŸ«ΆπŸ’–

πŸ“¦ where this page comes from