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

Lockdown mode #19

Merged
merged 3 commits into from
Jul 23, 2014
Merged

Lockdown mode #19

merged 3 commits into from
Jul 23, 2014

Conversation

arlimus
Copy link
Member

@arlimus arlimus commented Jul 23, 2014

  • Rename modules_disabled -> lockdown
  • Add all current requirements from default serverspecs to lockdown
  • Default tests for SUID/SGID bits only checks for blacklist now

arlimus added 3 commits July 23, 2014 15:46
I.e. create tests for a special hardening profile whose configuration is to lock down all settings. This will include scanning for all unkown SUID-bits as well as kernel configuration with module lockdown.

Signed-off-by: Dominik Richter <[email protected]>
Instead of going for the whitelist and expecting all other SUID/SGID bits to be removed, go for the blacklist in the default profile. This behavior is preferred, since we don't want to enable a search through all nodes on a system for any SUID/SGID bits by default. This search is desired and reasonable in all cases, but many new users will be turned away if we activate it by default. It causes issues with any regularly mounted network filesystems (which take very long) or very large (amount of entries on the filesystem) storage nodes.

We will add this point to the documentation, as it's the user's task to mount these components with a nosuid configuration.

Signed-off-by: Dominik Richter <[email protected]>
@atomic111
Copy link
Member

better solution, great, thank you

atomic111 pushed a commit that referenced this pull request Jul 23, 2014
@atomic111 atomic111 merged commit d2f57f2 into master Jul 23, 2014
@arlimus arlimus deleted the lockdown-mode branch August 13, 2014 09:01
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.

2 participants