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

Update some RH settings in this module #102

Closed
artem-sidorenko opened this issue Nov 7, 2017 · 2 comments
Closed

Update some RH settings in this module #102

artem-sidorenko opened this issue Nov 7, 2017 · 2 comments
Assignees
Milestone

Comments

@artem-sidorenko
Copy link
Member

artem-sidorenko commented Nov 7, 2017

See dev-sec/linux-baseline#82, this are definitely the better defaults for RH systems.

Chef implementation is in dev-sec/chef-os-hardening#177

@artem-sidorenko artem-sidorenko changed the title Update some RH settings in this cookbook Update some RH settings in this module Nov 7, 2017
mcgege added a commit to mcgege/puppet-os-hardening that referenced this issue Nov 10, 2017
Params for /etc/shadow moved to init.pp
Maybe we should bring all platform parameters into one file or hiera?

Signed-off-by: Michael Geiger <michael.geiger@telekom.de>
mcgege added a commit to mcgege/puppet-os-hardening that referenced this issue Nov 10, 2017
Params for /etc/shadow moved to init.pp
Maybe we should bring all platform parameters into one file or hiera?

Signed-off-by: Michael Geiger <michael.geiger@telekom.de>
mcgege added a commit to mcgege/puppet-os-hardening that referenced this issue Nov 10, 2017
Params for /etc/shadow moved to init.pp
Maybe we should bring all platform parameters into one file or hiera?

Signed-off-by: Michael Geiger <michael.geiger@telekom.de>
@mcgege
Copy link
Member

mcgege commented Nov 10, 2017

My proposal: #103

@mcgege mcgege added this to the 2.0.0 milestone Dec 19, 2017
@mcgege mcgege modified the milestones: 2.0.0, 2.1.0 Dec 19, 2017
artem-sidorenko added a commit that referenced this issue Dec 19, 2017
Implement new RH defaults (see issue #102)
@artem-sidorenko
Copy link
Member Author

Resolved via #103

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

No branches or pull requests

2 participants