Cherry-pick #19793 to 7.x: [Elastic Agent] Fix saving of agent configuration on Windows to have proper ACLs #19806
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.
Cherry-pick of PR #19793 to 7.x branch. Original message:
What does this PR do?
Currently Elastic Agent only set unix based permissions and did not set proper ACL's on Windows. This adds a new module
github.com/hectane/go-acl
that ensures that a call toacl.Chmod
sets the proper ACL on windows, just the same as it does on unix based systems.Why is it important?
Both the
fleet.yml
andaction_store.yml
can include sensitive information, so the information needs to have strong permissions so only users with enough permissions can read those files.Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Relates