RHEL7-CIS ansible-role pull-requests
39 views
Skip to first unread message
Bas Meijer
Jan 22, 2021, 5:56:02 AM1/22/21
to Ansible Lockdown
Hi,
In October I've opened 3 pull-requests on the RHEL7-CIS ansible-role. Is anyone willing and able to take a look and merge them?
These are meant to raise the bar for CIS compliance, as audited by Openscap & CISCAT-PRO:
#177 - Adding implementation for 5.3.2 lockout for failed password attempts.
#178 - Adding implementation for 5.4.1.4 inactive password lock 30 days.
#179 - Adding implemenation for 5.3.3 limiting password reuse.
https://github.com/ansible-lockdown/RHEL7-CIS/pulls/bbaassssiiee
kind regards, stay safe, sane & secure!
Bas Meijer
@bbaassssiiee
--
In October I've opened 3 pull-requests on the RHEL7-CIS ansible-role. Is anyone willing and able to take a look and merge them?
These are meant to raise the bar for CIS compliance, as audited by Openscap & CISCAT-PRO:
#177 - Adding implementation for 5.3.2 lockout for failed password attempts.
#178 - Adding implementation for 5.4.1.4 inactive password lock 30 days.
#179 - Adding implemenation for 5.3.3 limiting password reuse.
https://github.com/ansible-lockdown/RHEL7-CIS/pulls/bbaassssiiee
kind regards, stay safe, sane & secure!
Bas Meijer
@bbaassssiiee
--
Justin Nemmers
Jan 22, 2021, 8:04:23 AM1/22/21
to Bas Meijer, Ansible Lockdown
Hi Bas-
Around the time of your PR, we re-wrote much of the underlying Role. Your PRs will likely need to be refactored in order to account for those changes.
> On Jan 22, 2021, at 5:56 AM, Bas Meijer <brme...@gmail.com> wrote:
>
> Hi,
> --
> You received this message because you are subscribed to the Google Groups "Ansible Lockdown" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to ansible-lockdo...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-lockdown/6CF14859-BC85-4BDF-B1A2-DC583D45390B%40gmail.com.
Confidential: This email is intended for recipient to which it is addressed. The information contained in this email may be confidential, proprietary, or may contain PII. Any retransmission, review, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you have been asked to provide PII to the sender of this email, then in order to properly secure this information, please send it within an encrypted attachment with the password/key provided under a separate cover, such as in person, by phone, or in a separate email.
Around the time of your PR, we re-wrote much of the underlying Role. Your PRs will likely need to be refactored in order to account for those changes.
> On Jan 22, 2021, at 5:56 AM, Bas Meijer <brme...@gmail.com> wrote:
>
> Hi,
> You received this message because you are subscribed to the Google Groups "Ansible Lockdown" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to ansible-lockdo...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-lockdown/6CF14859-BC85-4BDF-B1A2-DC583D45390B%40gmail.com.
Confidential: This email is intended for recipient to which it is addressed. The information contained in this email may be confidential, proprietary, or may contain PII. Any retransmission, review, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you have been asked to provide PII to the sender of this email, then in order to properly secure this information, please send it within an encrypted attachment with the password/key provided under a separate cover, such as in person, by phone, or in a separate email.
Reply all
Reply to author
Forward
0 new messages