geoclue_selinux(8)

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

✨ geoclue_selinux β€” the SELinux manual page for geoclue_selinux(8), bestie edition ✨

okay so. this is the manual page for geoclue_selinux, and it's basically the whole lore drop on how SELinux keeps the geoclue processes in check. it's giving "security but make it fashionable." let's get into it πŸ’…


πŸ’– NAME πŸ’–

geoclue_selinux β€” the Security Enhanced Linux Policy for the geoclue processes. that's it, that's the name, no cap.


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the geoclue processes via flexible mandatory access control. lowkey powerful. it's not vibes-based security, it's actually enforced.

The geoclue processes execute with the geoclue_t SELinux type. and you can literally check if you have these processes running by executing the ps command with the -Z qualifier. like so:

ps -eZ | grep geoclue_t

run it, see what happens, live a little πŸ¦‹


πŸŽ€ ENTRYPOINTS πŸŽ€

The geoclue_t SELinux type can be entered via the geoclue_exec_t file type. that's the doorway, periodt.

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

/usr/lib/geoclue, /usr/libexec/geoclue

two paths, both iconic, both exactly as written, don't come for me πŸ”₯


πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system. yes, every single one gets a little label. main character energy for processes, honestly.

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

Policy governs the access confined processes have to files. SELinux geoclue policy is very flexible, allowing users to setup their geoclue processes in as secure a method as possible. flexible and secure? we love a multitasker ✨

The following process types are defined for geoclue:

geoclue_t
Note: semanage permissive -a geoclue_t can be used to make the process type geoclue_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like… it stops blocking, but it's still gonna talk about you behind your back. the receipts stay πŸ’€

🌈 BOOLEANS 🌈

SELinux policy is customizable based on least access required. geoclue policy is extremely flexible and has several booleans that allow you to manipulate the policy and run geoclue with the tightest access possible. tightest access = the fitted look, the tailored fit, we're obsessed πŸŽ€

  • 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 confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. Enabled by default.
setsebool -P kerberos_enabled 1
  • 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

four booleans, all enabled by default, all slaying in their own way πŸ’œ


πŸ¦‹ MANAGED FILES πŸ¦‹

The SELinux process type geoclue_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. and bestie, note this: the processes UID still need to have DAC permissions. SELinux isn't out here overriding DAC, it's just doing its own extra layer. iykyk 😭

  • 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
  • geoclue_tmp_t

(this one has no paths listed in the original, and we respect that. mysterious. elusive. we stan a private queen πŸ™ˆ)

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

πŸ’… FILE CONTEXTS πŸ’…

SELinux requires files to have an extended attribute to define the file type. it's not just a vibe, it's an xattr, fr fr.

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 geoclue policy is very flexible, allowing users to setup their geoclue processes in as secure a method as possible. said it once, saying it again, it's flexible and it's secure and it's that girl 🌸

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the geoclue. 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. like this, exactly like this:

semanage fcontext -a -t geoclue_exec_t '/srv/geoclue/content(/.*)?'
restorecon -R -v /srv/mygeoclue_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise 🧚

The following file types are defined for geoclue:

  • geoclue_exec_t β€” Set files with the geoclue_exec_t type, if you want to transition an executable to the geoclue_t domain.

Paths:

/usr/lib/geoclue, /usr/libexec/geoclue
  • geoclue_tmp_t β€” Set files with the geoclue_tmp_t type, if you want to store geoclue temporary files in the /tmp directories.
  • geoclue_var_lib_t β€” Set files with the geoclue_var_lib_t type, if you want to store the geoclue 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. ok so chcon is the "for now" girlie and semanage fcontext + restorecon is the "forever" commitment. choose wisely πŸ’€

🫢 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. a whole GUI! for the girlies who prefer clicking over typing πŸ–±οΈβœ¨

πŸ’œ AUTHOR πŸ’œ

This manual page was auto-generated using sepolicy manpage. so nobody hand-wrote this, the machine did it, and honestly? it ate.


πŸ”₯ SEE ALSO πŸ”₯

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

go read those next, bestie, that's your summer reading list πŸ“š


and that's the whole page! this one was brought to you by geoclue, dated 26-10-06, at version geoclue_selinux(8). mwah, go secure your processes πŸ’–

πŸ“¦ where this page comes from