gpsd_selinux(8)

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

πŸ’– gpsd_selinux(8) β€” the SELinux policy for gpsd, explained bestie to bestie πŸ’–

okay so this is the gpsd_selinux page from the SELinux Policy gpsd manual, and honestly? it's giving "security paperwork but make it cute." we're gonna go through it together, no skipped sections, no cap. 🫢


✨ NAME ✨

gpsd_selinux β€” the Security Enhanced Linux Policy for the gpsd processes. that's it, that's the whole name section, she's brief and iconic πŸ’…


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the gpsd processes via flexible mandatory access control. yes, mandatory β€” not the vibe of optional, she's mandatory, she's in charge, periodt.

the gpsd processes execute with the gpsd_t SELinux type. want to check if you've got these processes running? run the ps command with the -Z qualifier, like this:

ps -eZ | grep gpsd_t

boom. now you know. πŸ”₯


πŸ¦‹ ENTRYPOINTS πŸ¦‹

the gpsd_t SELinux type can be entered via the gpsd_exec_t file type β€” that's the doorway, that's the velvet rope.

the default entrypoint paths for the gpsd_t domain are literally just:

/usr/bin/gpsd

one path. one queen. πŸ‘‘


πŸ’œ PROCESS TYPES πŸ’œ

SELinux defines process types (domains) for each process running on the system. lowkey a whole taxonomy situation.

you can see the context of a process using the -Z option to ps β€” yes, same flex as before.

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

the following process types are defined for gpsd:

  • gpsd_t
Note: semanage permissive -a gpsd_t can be used to make the process type gpsd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like… she won't block you, but she will be watching and taking notes. 😭

πŸŽ€ BOOLEANS πŸŽ€

SELinux policy is customizable based on least access required. the gpsd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run gpsd with the tightest access possible. tightest access = the most locked-down, most modest, most "i'm not doing too much" setup. 🧚

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

three booleans, three little switches, all documented, nothing skipped. πŸ“


🌈 PORT TYPES 🌈

SELinux defines port types to represent TCP and UDP ports. yes bestie, ports get types too, everyone gets a label in this house.

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. the SELinux gpsd policy is very flexible, allowing users to setup their gpsd processes in as secure a method as possible. (yes, she says this a lot, she means it every time. πŸ’…)

the following port types are defined for gpsd:

  • gpsd_port_t

Default Defined Ports:

     tcp 2947

that's tcp 2947, write it down, don't lose it. ⭐


🫢 MANAGED FILES 🫢

the SELinux process type gpsd_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. SELinux said "i'll handle my layer, you handle yours." 😌

πŸ’– the file types πŸ’–

  • chronyd_tmpfs_t β€” no default paths listed, she's mysterious, she's a vibe.
  • 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
  • gpsd_tmpfs_t β€” again, no paths listed. she's on tmpfs, she doesn't need to explain herself.
  • gpsd_var_run_t
/run/gpsd.pid
/run/gpsd.sock
  • 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
  • ntpd_tmpfs_t β€” no paths. tiny, quiet, iconic.
  • root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
  • timemaster_tmpfs_t β€” no paths listed. she's just here, living her life. 🌸

πŸ”₯ FILE CONTEXTS πŸ”₯

SELinux requires files to have an extended attribute to define the file type. it's not just a filename situation, it's a whole extended attribute situation.

you can see the context of a file using the -Z option to ls β€” same -Z energy, different command.

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

πŸ’œ STANDARD FILE CONTEXT πŸ’œ

SELinux defines the file context types for the gpsd. 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. like so:

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

the following file types are defined for gpsd:

πŸ’… gpsd_exec_t

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

πŸ’… gpsd_initrc_exec_t

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

πŸ’… gpsd_tmp_t

  • Set files with the gpsd_tmp_t type, if you want to store gpsd temporary files in the /tmp directories.

πŸ’… gpsd_tmpfs_t

  • Set files with the gpsd_tmpfs_t type, if you want to store gpsd files on a tmpfs file system.

πŸ’… gpsd_var_run_t

  • Set files with the gpsd_var_run_t type, if you want to store the gpsd files under the /run or /var/run directory.

Paths:

     /run/gpsd.pid, /run/gpsd.sock
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 quick outfit change, semanage fcontext + restorecon is the actual closet reorg. don't confuse them, 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. GUI girlies, this one's for you. πŸ–₯️✨

🌟 AUTHOR 🌟

This manual page was auto-generated using sepolicy manpage . (yes, a robot wrote it, and she ate. πŸ€–πŸ’…)


πŸ‘‘ SEE ALSO πŸ‘‘

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

all seven, all linked, go read them, iykyk. πŸ¦‹


and that's the whole page!! mwah πŸ’– big kiss, stay labeled correctly, and remember: this was gpsd, dated 26-10-06, straight from the gpsd_selinux(8) manual. periodt. πŸŽ€

πŸ“¦ where this page comes from