Auto Installer #242
Open
Auto Installer #242
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello and welcome to this repository ! Could you elaborate the need of an install.sh script for DoD compliance ? Are we talking about USA Department of Defense compliance here ? At first sight, you script is basically implementing what's written in the README.md, but on quick and dirty way. I mean that this repository is intended to makje machines remain compliant in the long run, and as such, hardening.sh has been coded accordingly (to fit in to a crontab for example). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Key Enhancements for DoD Compliance
Logging: Added comprehensive logging of actions and errors to /var/log/debian-cis-hardening.log. This ensures traceability and accountability.
Error Handling: Included checks for the success of each operation and exit on failure, which helps maintain the integrity of the script and provides immediate feedback on issues.
Root Privileges Check: Ensures the script is executed with root privileges, which is crucial for performing system-wide configurations.
Backup of Existing Configurations: Provides backup of existing configuration files before making changes.
Secure Permissions: Sets secure permissions for the log file to protect sensitive audit information.
User Interaction: Prompts user for additional options and configurations, ensuring the script is flexible and adaptable to various requirements.