[Openstack-security] [Bug 1616281] [NEW] Can't initialize AIDE during subsequent playbook runs

Major Hayden major at mhtx.net
Wed Aug 24 02:30:02 UTC 2016


Public bug reported:

AIDE isn't initialized by default because it can cause a lot of system
load when it does its first check of a new system. If a deployer applies
the security hardening role with ``initialize_aide`` set to False (the
default), it won't be initialized. However, if they set it to True and
re-run the playbook, AIDE is already configured and the handler to
initialize AIDE won't execute.

** Affects: openstack-ansible
     Importance: Medium
     Assignee: Major Hayden (rackerhacker)
         Status: New


** Tags: security

-- 
You received this bug notification because you are a member of OpenStack
Security, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1616281

Title:
  Can't initialize AIDE during subsequent playbook runs

Status in openstack-ansible:
  New

Bug description:
  AIDE isn't initialized by default because it can cause a lot of system
  load when it does its first check of a new system. If a deployer
  applies the security hardening role with ``initialize_aide`` set to
  False (the default), it won't be initialized. However, if they set it
  to True and re-run the playbook, AIDE is already configured and the
  handler to initialize AIDE won't execute.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-ansible/+bug/1616281/+subscriptions




More information about the Openstack-security mailing list