TELEPATHY_MISSION_CONTROL_SELINUX(8)

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

πŸ’– NAME

okay bestie, this is the telepathy_mission_control_selinux(8) page β€” the Security Enhanced Linux Policy one for the telepathy_mission_control processes. We're in the SELinux Policy telepathy_mission_control manual, section 8. ✨

🌸 DESCRIPTION

Security-Enhanced Linux secures the telepathy_mission_control processes via flexible mandatory access control. No cap, that's the whole point.

The telepathy_mission_control processes execute with the telepathy_mission_control_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 telepathy_mission_control_t

πŸšͺ ENTRYPOINTS

The telepathy_mission_control_t SELinux type can be entered via the telepathy_mission_control_exec_t file type.

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

  • /usr/libexec/mission-control-5

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

The following process types are defined for telepathy_mission_control:

  • telepathy_mission_control_t
note: semanage permissive -a telepathy_mission_control_t can be used to make the process type telepathy_mission_control_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, don't think it goes fully silent πŸ‘€

πŸŽ€ BOOLEANS

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

  • 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. Command:
setsebool -P fips_mode 1
  • nis_enabled β€” if you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default. Command:
setsebool -P nis_enabled 1

πŸ’Ύ MANAGED FILES

The SELinux process type telepathy_mission_control_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 need to have DAC permissions β€” SELinux is not out here overriding that, bestie.

  • cache_home_t
    • /root/.cache(/.*)?
    • /home/[^/]+/.nv(/.*)?
    • /home/[^/]+/.cache(/.*)?
  • cifs_t β€” no default paths listed on this page.
  • config_home_t
    • /root/.kde(/.*)?
    • /root/.xine(/.*)?
    • /root/.config(/.*)?
    • /root/.Xdefaults
    • /home/[^/]+/.kde(/.*)?
    • /home/[^/]+/.xine(/.*)?
    • /home/[^/]+/.config(/.*)?
    • /home/[^/]+/.cache/dconf(/.*)?
    • /home/[^/]+/.Xdefaults
    • /run/user/[0-9]+/dconf(/.*)?
  • 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 β€” no default paths listed on this page.
  • telepathy_gabble_cache_home_t
    • /home/[^/]+/.cache/wocky(/.*)?
    • /home/[^/]+/.cache/telepathy/gabble(/.*)?
    • /home/[^/]+/.cache/telepathy/avatars/gabble(/.*)?
  • telepathy_mission_control_cache_home_t
    • /home/[^/]+/.cache/.mc_connections
  • telepathy_mission_control_data_home_t
    • /home/[^/]+/.local/share/telepathy/mission-control(/.*)?
  • telepathy_mission_control_home_t
    • /home/[^/]+/.mission-control(/.*)?
  • telepathy_mission_control_tmp_t β€” no default paths listed on this page.

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

🌈 STANDARD FILE CONTEXT

SELinux defines the file context types for telepathy_mission_control. 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 telepathy_mission_control_exec_t '/srv/telepathy_mission_control/content(/.*)?'
restorecon -R -v /srv/mytelepathy_mission_control_content
note: SELinux often uses regular expressions to specify labels that match multiple files. iykyk πŸ‘‘

The following file types are defined for telepathy_mission_control:

  • telepathy_mission_control_cache_home_t β€” set files with the telepathy_mission_control_cache_home_t type if you want to store telepathy mission control cache files in the user's home directory.
  • telepathy_mission_control_data_home_t β€” set files with the telepathy_mission_control_data_home_t type if you want to store telepathy mission control data files in the user's home directory.
  • telepathy_mission_control_exec_t β€” set files with the telepathy_mission_control_exec_t type if you want to transition an executable to the telepathy_mission_control_t domain.
  • telepathy_mission_control_home_t β€” set files with the telepathy_mission_control_home_t type if you want to store telepathy mission control files in the user's home directory.
  • telepathy_mission_control_tmp_t β€” set files with the telepathy_mission_control_tmp_t type if you want to store telepathy mission control temporary files in the /tmp directories.
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. periodt πŸ’…

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

πŸ’œ SEE ALSO

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


bye bestie! signing off from the telepathy_mission_control page, version/date 26-10-06, living under telepa...selinux(8) β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from