xend_selinux(8)

๐Ÿ“ฆ
version 20250627+git412.dbf877ab7 ยท 7 versions
, in opensuse-leap 16.0

โœจ xend_selinux(8) โœจ

okay so bestie, welcome to the xend_selinux(8) page โ€” this is the whole SELinux policy tea for xend processes and it's literally giving main character energy. let me walk you through it.

๐ŸŒธ NAME ๐ŸŒธ

xend_selinux โ€” the Security Enhanced Linux Policy for the xend processes. periodt.

๐Ÿ’… DESCRIPTION ๐Ÿ’…

Security-Enhanced Linux secures the xend processes via flexible mandatory access control. basically SELinux is the bodyguard for your xend processes and it's very thorough, no cap.

the xend processes execute with the xend_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 xend_t

run that and see what's up, bestie.

๐Ÿฆ‹ ENTRYPOINTS ๐Ÿฆ‹

the xend_t SELinux type can be entered via the xend_exec_t file type.

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

/usr/bin/xend

that's the one ๐Ÿ‘‘

โญ PROCESS TYPES โญ

SELinux defines process types (domains) for each process running on the system โ€” so every process gets its own little label, slay.

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

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

the following process types are defined for xend:

  • xend_t โ€” that's the one and only, the icon.
Note: semanage permissive -a xend_t can be used to make the process type xend_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated โ€” so like, you'll still see the drama in the logs, but it won't actually block anything. iykyk.

๐Ÿ“ BOOLEANS ๐Ÿ“

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

here's the tea, bestie:

  • xen_use_nfs โ€” if you want to allow xen to manage nfs files, you must turn on the xen_use_nfs boolean. Disabled by default.
setsebool -P xen_use_nfs 1
  • xend_run_blktap โ€” if you want to allow xend to run blktapctrl/tapdisk. Not required if using dedicated logical volumes for disk images, you must turn on the xend_run_blktap boolean. Enabled by default.
setsebool -P xend_run_blktap 1
  • xend_run_qemu โ€” if you want to allow xend to run qemu-dm. Not required if using paravirt and no vfb, you must turn on the xend_run_qemu boolean. Enabled by default.
setsebool -P xend_run_qemu 1
  • 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

๐Ÿ”ฎ 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 xend policy is very flexible allowing users to setup their xend processes in as secure a method as possible.

the following port types are defined for xend:

  • xen_port_t โ€” the port type, periodt.

Default Defined Ports:

tcp 8002

that's the port, no cap ๐Ÿซถ

๐Ÿ‘‘ MANAGED FILES ๐Ÿ‘‘

the SELinux process type xend_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 โ€” so like, SELinux doesn't override normal permissions, it's extra.

  • 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
  • dhcp_etc_t
    • /etc/dhcpc.*
    • /etc/dhcp3?(/.*)?
    • /etc/dhcpd(6)?.conf
    • /etc/dhcp3?/dhclient.*
    • /etc/dhclient.*conf
    • /etc/dhcp/dhcpd(6)?.conf
    • /etc/dhclient-script
  • nfs_t โ€” no default paths listed, it's just vibes.
  • root_t
    • /sysroot/.aleph-version.json
    • /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
    • /
    • /initrd
    • /var/lib/ntp
  • sysfs_t
    • /sys(/.*)?
  • virt_image_t
    • /var/lib/libvirt/images(/.*)?
    • /var/lib/imagefactory/images(/.*)?
  • xen_image_t
    • /xen(/.*)?
    • /var/lib/xen/images(/.*)?
  • xend_tmp_t โ€” no default paths listed.
  • xend_var_lib_t
    • /var/lib/xen(/.*)?
    • /var/lib/xend(/.*)?
  • xend_var_log_t
    • /var/log/xen(/.*)?
    • /var/log/xend.log.*
    • /var/log/xend-debug.log.*
    • /var/log/xen-hotplug.log.*
  • xend_var_run_t
    • /run/xend(/.*)?
    • /run/xenner(/.*)?
    • /run/xend.pid
  • xenfs_t โ€” no default paths listed.
  • xenstored_var_run_t
    • /run/xenstored(/.*)?
    • /run/xenstore.pid

๐ŸŒˆ 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 xend policy is very flexible allowing users to setup their xend processes in as secure a method as possible.

๐Ÿ’š EQUIVALENCE DIRECTORIES ๐Ÿ’š

xend policy stores data with multiple different file context types under the /var/lib/xen directory. if you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. if you wanted to store this data under the /srv directory you would execute the following command:

semanage fcontext -a -e /var/lib/xen /srv/xen
restorecon -R -v /srv/xen

xend policy stores data with multiple different file context types under the /var/log/xen directory. if you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. if you wanted to store this data under the /srv directory you would execute the following command:

semanage fcontext -a -e /var/log/xen /srv/xen
restorecon -R -v /srv/xen

๐Ÿ’™ STANDARD FILE CONTEXT ๐Ÿ’™

SELinux defines the file context types for the xend, 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.

semanage fcontext -a -t xend_exec_t '/srv/xend/content(/.*)?'
restorecon -R -v /srv/myxend_content
Note: SELinux often uses regular expressions to specify labels that match multiple files.

the following file types are defined for xend:

  • xend_exec_t โ€” set files with the xend_exec_t type, if you want to transition an executable to the xend_t domain.
  • xend_tmp_t โ€” set files with the xend_tmp_t type, if you want to store xend temporary files in the /tmp directories.
  • xend_var_lib_t โ€” set files with the xend_var_lib_t type, if you want to store the xend files under the /var/lib directory.

Paths:

  • /var/lib/xen(/.*)?
  • /var/lib/xend(/.*)?
  • xend_var_log_t โ€” set files with the xend_var_log_t type, if you want to treat the data as xend var log data, usually stored under the /var/log directory.

Paths:

  • /var/log/xen(/.*)?
  • /var/log/xend.log.*
  • /var/log/xend-debug.log.*
  • /var/log/xen-hotplug.log.*
  • xend_var_run_t โ€” set files with the xend_var_run_t type, if you want to store the xend files under the /run or /var/run directory.

Paths:

  • /run/xend(/.*)?
  • /run/xenner(/.*)?
  • /run/xend.pid
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.

๐Ÿ’ป COMMANDS ๐Ÿ’ป

here's the tools you can use, bestie:

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

โœ๏ธ AUTHOR โœ๏ธ

this manual page was auto-generated using sepolicy manpage โ€” not me writing it by hand, okay? but the vibe is all me ๐Ÿ’…

๐Ÿ”— SEE ALSO ๐Ÿ”—


๐Ÿ’– stay slay, bestie โ€” this page is from the xend source, dated 26-10-06, and it's the xend_selinux(8) manual. periodt. ๐Ÿ’–

๐Ÿ“ฆ where this page comes from