swift_selinux

Section: SELinux Policy swift (8)
Updated: 19-05-26
Page Index
 

NAME

swift_selinux - Security Enhanced Linux Policy for the swift processes  

DESCRIPTION

Security-Enhanced Linux secures the swift processes via flexible mandatory access control.

The swift processes execute with the swift_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 swift_t

 

ENTRYPOINTS

The swift_t SELinux type can be entered via the swift_exec_t file type.

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

/usr/bin/swift-object-info, /usr/bin/swift-proxy-server, /usr/bin/swift-object-server, /usr/bin/swift-account-reaper, /usr/bin/swift-account-server, /usr/bin/swift-container-sync, /usr/bin/swift-object-auditor, /usr/bin/swift-object-expirer, /usr/bin/swift-object-updater, /usr/bin/swift-account-auditor, /usr/bin/swift-container-server, /usr/bin/swift-container-auditor, /usr/bin/swift-container-updater, /usr/bin/swift-object-replicator, /usr/bin/swift-account-replicator, /usr/bin/swift-container-reconciler, /usr/bin/swift-container-replicator  

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 psP Policy governs the access confined processes have to files. SELinux swift policy is very flexible allowing users to setup their swift processes in as secure a method as possible.

The following process types are defined for swift:

swift_t

Note: semanage permissive -a swift_t can be used to make the process type swift_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.

 

BOOLEANS

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

If you want to determine whether swift can connect to all TCP ports, you must turn on the swift_can_network boolean. Disabled by default.

setsebool -P swift_can_network 1

If you want to allow users to resolve user passwd entries directly from ldap rather then using a sssd server, you must turn on the authlogin_nsswitch_use_ldap boolean. Disabled by default.

setsebool -P authlogin_nsswitch_use_ldap 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 system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.

setsebool -P nis_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

 

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

The following port types are defined for swift:

swift_port_t

Default Defined Ports: tcp 6200-6203

 

MANAGED FILES

The SELinux process type swift_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.


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

        /var/run/crm(/.*)?

       /var/run/cman_.*

       /var/run/rsctmp(/.*)?

       /var/run/aisexec.*

       /var/run/heartbeat(/.*)?

       /var/run/corosync-qnetd(/.*)?

       /var/run/corosync-qdevice(/.*)?

       /var/run/corosync.pid

       /var/run/cpglockd.pid

       /var/run/rgmanager.pid

       /var/run/cluster/rgmanager.sk


root_t

        /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?

       /

       /initrd


swift_data_t

        /srv/node(/.*)?

       /var/lib/swift(/.*)?

       /srv/loopback-device(/.*)?


swift_lock_t

        /var/lock/swift.*


swift_tmp_t


swift_tmpfs_t


swift_var_cache_t

        /var/cache/swift(/.*)?


swift_var_run_t

        /var/run/swift(/.*)?

 

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 lsP Policy governs the access confined processes have to these files. SELinux swift policy is very flexible allowing users to setup their swift processes in as secure a method as possible.

STANDARD FILE CONTEXT

SELinux defines the file context types for the swift, if you wanted to store files with these types in a diffent paths, you need to execute the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk.

semanage fcontext -a -t swift_data_t '/srv/myswift_content(/.*)?'
restorecon -R -v /srv/myswift_content

Note: SELinux often uses regular expressions to specify labels that match multiple files.

The following file types are defined for swift:

swift_data_t

- Set files with the swift_data_t type, if you want to treat the files as swift content.


Paths:
/srv/node(/.*)?, /var/lib/swift(/.*)?, /srv/loopback-device(/.*)?

swift_exec_t

- Set files with the swift_exec_t type, if you want to transition an executable to the swift_t domain.


Paths:
/usr/bin/swift-object-info, /usr/bin/swift-proxy-server, /usr/bin/swift-object-server, /usr/bin/swift-account-reaper, /usr/bin/swift-account-server, /usr/bin/swift-container-sync, /usr/bin/swift-object-auditor, /usr/bin/swift-object-expirer, /usr/bin/swift-object-updater, /usr/bin/swift-account-auditor, /usr/bin/swift-container-server, /usr/bin/swift-container-auditor, /usr/bin/swift-container-updater, /usr/bin/swift-object-replicator, /usr/bin/swift-account-replicator, /usr/bin/swift-container-reconciler, /usr/bin/swift-container-replicator

swift_lock_t

- Set files with the swift_lock_t type, if you want to treat the files as swift lock data, stored under the /var/lock directory

swift_tmp_t

- Set files with the swift_tmp_t type, if you want to store swift temporary files in the /tmp directories.

swift_tmpfs_t

- Set files with the swift_tmpfs_t type, if you want to store swift files on a tmpfs file system.

swift_unit_file_t

- Set files with the swift_unit_file_t type, if you want to treat the files as swift unit content.

swift_var_cache_t

- Set files with the swift_var_cache_t type, if you want to store the files under the /var/cache directory.

swift_var_run_t

- Set files with the swift_var_run_t type, if you want to store the swift files under the /run or /var/run 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.

 

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.

 

AUTHOR

This manual page was auto-generated using sepolicy manpage.

 

SEE ALSO

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

Index

NAME
DESCRIPTION
ENTRYPOINTS
PROCESS TYPES
BOOLEANS
PORT TYPES
MANAGED FILES
FILE CONTEXTS
COMMANDS
AUTHOR
SEE ALSO