-
Notifications
You must be signed in to change notification settings - Fork 23
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
/opt/AMAZON2-CIS-Audit/run_audit.sh: Permission denied #19
Labels
bug
Something isn't working
Comments
hi @swestcott Many thanks for raising this issue, I am happy to include in the next PR to devel. hopefully to be merged later this week. regards uk-bolly |
uk-bolly
added a commit
that referenced
this issue
May 16, 2023
Signed-off-by: Mark Bolwell <[email protected]>
Merged
Merged
uk-bolly
added a commit
that referenced
this issue
May 1, 2024
* #18 corrected Signed-off-by: Mark Bolwell <[email protected]> * updated due to #19 great catch Signed-off-by: Mark Bolwell <[email protected]> * V2.0.0 final release (#24) * removed warn: false Signed-off-by: Mark Bolwell <[email protected]> * fix typos Signed-off-by: Mark Bolwell <[email protected]> * addressed #21 Signed-off-by: Mark Bolwell <[email protected]> * updated 1.1.2 logic Signed-off-by: Mark Bolwell <[email protected]> * updated handler Signed-off-by: Mark Bolwell <[email protected]> --------- Signed-off-by: Mark Bolwell <[email protected]> * Correct 4.1.15 sudo audit syntax (#26) Signed-off-by: Andrew Davison <[email protected]> --------- Signed-off-by: Mark Bolwell <[email protected]> Signed-off-by: Andrew Davison <[email protected]> Co-authored-by: Andrew Davison <[email protected]>
mfortin
pushed a commit
to mfortin/AMAZON2-CIS
that referenced
this issue
Jun 7, 2024
Signed-off-by: Mark Bolwell <[email protected]> Signed-off-by: fortinm <[email protected]>
mfortin
pushed a commit
to mfortin/AMAZON2-CIS
that referenced
this issue
Jun 7, 2024
* ansible-lockdown#18 corrected Signed-off-by: Mark Bolwell <[email protected]> * updated due to ansible-lockdown#19 great catch Signed-off-by: Mark Bolwell <[email protected]> * V2.0.0 final release (ansible-lockdown#24) * removed warn: false Signed-off-by: Mark Bolwell <[email protected]> * fix typos Signed-off-by: Mark Bolwell <[email protected]> * addressed ansible-lockdown#21 Signed-off-by: Mark Bolwell <[email protected]> * updated 1.1.2 logic Signed-off-by: Mark Bolwell <[email protected]> * updated handler Signed-off-by: Mark Bolwell <[email protected]> --------- Signed-off-by: Mark Bolwell <[email protected]> * Correct 4.1.15 sudo audit syntax (ansible-lockdown#26) Signed-off-by: Andrew Davison <[email protected]> --------- Signed-off-by: Mark Bolwell <[email protected]> Signed-off-by: Andrew Davison <[email protected]> Co-authored-by: Andrew Davison <[email protected]> Signed-off-by: fortinm <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Issue
As per #18, I'm running in an environment without internet access so I need to copy the audit file to the server.
Relevant config,
Expected Behavior
Ansible is able to execute the run_audit.sh script
Actual Behavior
run_audit.sh fails to run as it's missing the execute bit
Environment (please complete the following information):
As per #18
Additional Notes
When the Audit files are copied to the remote host, the file permissions are set to 0644, thereby removing the execute bit(s) on all files, including run_audit.sh
https://github.com/ansible-lockdown/AMAZON2-CIS/blob/devel/tasks/pre_remediation_audit.yml#L33-L39
Possible Solution
Either preserve or re-add the execute bit on run_audit.sh
The text was updated successfully, but these errors were encountered: