openstack/openstack-ansible-security
Code Issues Proposed changes
fe39a30c98
openstack-ansible-security/doc/metadata/rhel6/V-38674.rst
Andy McCrae fe39a30c98 Revert "Retire openstack-ansible-security" 
This reverts commit ea9b39d723.
In order to release stable/pike we need this to still be present.
https://review.openstack.org/#/c/502063/ is failing.

Once we release stable/pike we can figure out how to properly remove
this repository.

Change-Id: I50308b1c3001371d4554b6c2640bd5384e870a53
2017-09-13 10:34:55 -06:00

1.1 KiB
Raw Blame History

---id: V-38674 status: implemented tag: x11 ---

In Ubuntu 14.04, the upstart init system looks for the default runlevel in the /etc/init/rc-sysinit.conf file. The tasks in the security role will ensure that the DEFAULT_RUNLEVEL environment variable is set to 2, which is a non-graphical runlevel.

In Ubuntu 16.04 and CentOS 7, systemd handles various targets, which are similar to runlevels from earlier init systems. There are two targets that are important for this STIG:

  • graphical.target: similar to runlevel 5 from earlier init systems
  • multi-user.target: similar to runlevel 2 or 3 from earlier init systems

The tasks in the security role will ensure that the default target is the multi-user.target, which provides a text-based system.

Deployers can opt out of this change by setting an Ansible variable:

security_disable_x_windows: no

Note

This change will not take effect until the server is rebooted. Changing a runlevel on an actively running system can cause certain services to stop, start, or restart.