Describe the bug
Modifying /etc/pam.d/system-auth-ac as seen here is wrong as it "breaks" the authconfig way. Apparently a symptom was also witnessed in #23.

Normally the file begins with:

#%PAM-1.0
# This file is auto-generated.
# User changes will be dest

v.5.0.3

var RBAC = require('rbac');

return

{ __esModule: true,
  RBAC: [Function: RBAC],
  Base: [Function: Base],
  Role: [Function: Role],
  Permission: [Function: Permission],
  Storage: [Function: Storage],
  Memory: [Function: Memory] }

in doc you wrote
var RBAC = require('rbac').default

Where is default key?
var RBAC = require('rbac').default
return **

We'd like to support CentOS8!

Ideally we'd have testing for:

• kitchen with vagrant (https://github.com/dev-sec/ansible-ssh-hardening/blob/master/.kitchen.vagrant.yml)
• kitchen with docker (https://github.com/dev-sec/ansible-ssh-hardening/blob/master/.kitchen.yml)
• travis (https://github.com/dev-sec/ansible-ssh-hardening/blob/master/.travis.yml)

Docker-Image that should be used: https

# fc29
dnf install -y docker docker-compose

# docker-1.13.1-62.git9cb56fd.fc29.src.rpm
# docker-compose-1.22.0-2.fc29.src.rpm

What's a good way to make this (only installing from a limited set of package repos) optional?

So, Ubuntu (18.04 at least) installs a cronjob and makes use of renewal-hooks directories. I can't find much documentation about it, but there is a bug report here: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1706409

There is some documentation on about the renewal-hooks directories:
https://certbot.eff.org/docs/using.html#renewing-certificates

I'm thinking about how I can

1. libmysqlclient-dev is default-libmysqlclient-dev on Deb 9 stretch.
2. Documentation: git should listed in Dependencies for building from source.
3. I had to add --without-sqlite3 and --without-pdo-sqlite to php_source_configure_command to work properly. Getting a current version of sqlite3 onto Debian 9 is a pain.

Play that I used for prep/patch:

---
- name: Install prer

Based on the current README my expectation was that the certificate_file, certificate_key_file and certificate_chain_file directives needed to point to local (on the ansible control node) which would get installed by the role.

It turns out that the paths are entered in the vhosts.conf.
No files are deployed so the playbook needs to handle that outisde this role.

I believe it would be useful

Documentation says priv: # defaults to not set. It should be great to know the format to specify the privilege of the user.

From Kubelet's startup logs via journalctl -f, when running Kubernetes 1.10+:

Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Flag --resolv-conf has been deprecated, This parameter should be set via the co

We'd like to support CentOS8!

Ideally we'd have testing for:

• kitchen with vagrant (https://github.com/dev-sec/ansible-nginx-hardening/blob/master/.kitchen.vagrant.yml)
• kitchen with docker (https://github.com/dev-sec/ansible-nginx-hardening/blob/master/.kitchen.yml)
• travis (https://github.com/dev-sec/ansible-nginx-hardening/blob/master/.travis.yml)

Docker-Image that should be used:

We'd like to support CentOS8!

Ideally we'd have testing for:

• kitchen with vagrant (https://github.com/dev-sec/ansible-mysql-hardening/blob/master/.kitchen.vagrant.yml)
• kitchen with docker (https://github.com/dev-sec/ansible-mysql-hardening/blob/master/.kitchen.yml)
• travis (https://github.com/dev-sec/ansible-mysql-hardening/blob/master/.travis.yml)

Docker-Image that should be used: