7473a45d98
This patch drops the offline option because this role usually applies to always-on machines and the subsystem which detects if you're online or offline seems to be largely unstable which causes chronyd to never attempt to synchronize time. It also drops the minpoll and maxpoll options to leave it to the defaults of the chronyd service, this is due to the numbers provided not allowing the system to properly sync up time. It also adds the 'iburst' option which will send a few quick bursts when the system first goes up in order to get it to sync up with time faster. Change-Id: Iad41ef505f5a1c142ec7ffe07e4a1c08aa614235
ansible-hardening
The ansible-hardening role applies security hardening configurations from the Security Technical Implementation Guide (STIG) to systems running the following distributions:
- CentOS 7
- Debian Jessie
- Fedora 27
- openSUSE Leap 42.2 and 42.3
- Red Hat Enterprise Linux 7
- SUSE Linux Enterprise 12 (experimental)
- Ubuntu 16.04
For more details, review the ansible-hardening documentation.
Release notes for the project can be found at: https://docs.openstack.org/releasenotes/ansible-hardening
Requirements
This role can be used with or without OpenStack-Ansible. It requires Ansible 2.3 or later.
Role Variables
All of the variables for this role are in defaults/main.yml.
Dependencies
This role has no dependencies.
Example Playbook
Using the role is fairly straightforward:
- hosts: servers
roles:
- ansible-hardening
Running with Vagrant
This role can be tested easily on multiple platforms using Vagrant.
The Vagrantfile supports testing on:
- Ubuntu 16.04
- CentOS 7
To test on all platforms:
vagrant destroy --force && vagrant up
To test on Ubuntu 14.04 only:
vagrant destroy ubuntu1404 --force && vagrant up ubuntu1404
To test on Ubuntu 16.04 only:
vagrant destroy ubuntu1604 --force && vagrant up ubuntu1604
To test on CentOS 7 only:
vagrant destroy centos7 --force && vagrant up centos7
License
Apache 2.0
Author Information
For more information, join #openstack-ansible on Freenode.