Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

5.6.1.1 Adding solution for users with passwords. #116

Conversation

brisky
Copy link
Contributor

@brisky brisky commented Nov 16, 2023

Overall Review of Changes:
Adds mesure to address existing users with password set.

Issue Fixes:
Fixes #113

Enhancements:
Checks for users with password set and sets expiration to 365 days.

How has this been tested?:
Manually and with ansible lockdown package, using vanilla installation.

uk-bolly and others added 25 commits March 21, 2023 15:39
…s/rhel9/devel'

Adding missing lines to sysctl.d/50-default.conf

See merge request infosec-pss-gov/security-crafter-baseline-automations/ansible-lockdown/rhel9-cis!1
…ens/rhel9/devel'

Adding new entry in /etc/pam.d/system-auth

See merge request infosec-pss-gov/security-crafter-baseline-automations/ansible-lockdown/rhel9-cis!2
…siemens/rhel9/devel'

Fix sintax Error on cis_5.2.x.yml

See merge request infosec-pss-gov/security-crafter-baseline-automations/ansible-lockdown/rhel9-cis!4
…emens.com:infosec-pss-gov/security-crafter-baseline-automations/ansible-lockdown/rhel9-cis into siemens/feat/ensure_default_umask_027_5_6_5
…ens/rhel9/devel'

Fix sintax Error on cis_5.2.x.yml

See merge request infosec-pss-gov/security-crafter-baseline-automations/ansible-lockdown/rhel9-cis!5
…siemens/rhel9/devel'

Fix regex with commented entries avoid dupes.

See merge request infosec-pss-gov/security-crafter-baseline-automations/ansible-lockdown/rhel9-cis!6
Signed-off-by: root@DERVISHx <[email protected]>
@brisky brisky closed this Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5.6.1.1 Ensure password expiration is 365 days or less
3 participants