aa1feb4527
With current behaviour we duplicate SSH options and don't care if same thing is defined anywhere down the line. With that change we change how options are defined - instead of the template we use a list of mappings. With that we can select and remove options that playbook supposed to manage. With that we also keep playbook idempotency. As side effect we still can have options duplicated but only if they have exact same value. Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/840353 Change-Id: I140606f7e724fbe2a4f0b03f6a0501da7bdd5964 Closes-Bug: #1958649
ansible-hardening
The ansible-hardening role applies security hardening configurations from the Security Technical Implementation Guide (STIG) to systems running the following distributions:
- CentOS 8
- Debian Buster
- Ubuntu Bionic
- Ubuntu Focal
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 OFTC.