jetty_selinux - Man Page

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

The jetty processes execute with the jetty_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 jetty_t

The jetty_t SELinux type can be entered via the jetty_exec_t file type.

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

/usr/share/jetty/bin/jetty.sh

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 psbP

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

The following process types are defined for jetty:

jetty_t

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

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

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

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

/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

jetty_cache_t

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

jetty_log_t

/var/log/jetty(/.*)?

jetty_tmp_t

jetty_var_lib_t

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

jetty_var_run_t

/run/jetty(/.*)?

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

root_t

/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd

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 lsbP

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

STANDARD FILE CONTEXT

SELinux defines the file context types for the jetty, 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 jetty_exec_t '/srv/jetty/content(/.*)?'
restorecon -R -v /srv/myjetty_content

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

The following file types are defined for jetty:

jetty_cache_t

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

jetty_exec_t

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

jetty_log_t

- Set files with the jetty_log_t type, if you want to treat the data as jetty log data, usually stored under the /var/log directory.

jetty_tmp_t

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

jetty_unit_file_t

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

jetty_var_lib_t

- Set files with the jetty_var_lib_t type, if you want to store the jetty files under the /var/lib directory.

jetty_var_run_t

- Set files with the jetty_var_run_t type, if you want to store the jetty 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.

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.

This manual page was auto-generated using sepolicy manpage .

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