-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
heartbeat - move seccomp customization to InitializeModule #39763
heartbeat - move seccomp customization to InitializeModule #39763
Conversation
Move the overwriting of the arm64 seccomp policy out of the Go init() phase and into a function call that is specific to Heartbeat. This will prevent Heartbeat's policy from affecting all other Beats that run as part of Agentbeat. Note that other customizations from all Beats that use seccomp.ModifyDefaultPolicy within init() are being combined in Agentbeat to create a policy that is the aggregation of all seccomp customizations. So the allow-list type policies are likely more permissive than expected. Fixes elastic#39754
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Move the overwriting of the arm64 seccomp policy out of the Go init() phase and into a function call that is specific to Heartbeat. This will prevent Heartbeat's policy from affecting all other Beats that run as part of Agentbeat. Note that other customizations from all Beats that use seccomp.ModifyDefaultPolicy within init() are still being combined in Agentbeat to create a policy that is the aggregation of all seccomp customizations. So the allow-list type policies are likely more permissive than expected. Fixes #39754 (cherry picked from commit 48a9901)
…39764) Move the overwriting of the arm64 seccomp policy out of the Go init() phase and into a function call that is specific to Heartbeat. This will prevent Heartbeat's policy from affecting all other Beats that run as part of Agentbeat. Note that other customizations from all Beats that use seccomp.ModifyDefaultPolicy within init() are still being combined in Agentbeat to create a policy that is the aggregation of all seccomp customizations. So the allow-list type policies are likely more permissive than expected. Fixes #39754 (cherry picked from commit 48a9901) Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
Proposed commit message
Move the overwriting of the arm64 seccomp policy out of the Go init() phase and into a function call that is specific to Heartbeat. This will prevent Heartbeat's policy from affecting all other Beats that run as part of Agentbeat.
Note that other customizations from all Beats that use seccomp.ModifyDefaultPolicy within init() are still being combined in Agentbeat to create a policy that is the aggregation of all seccomp customizations. So the allow-list type policies are likely more permissive than expected.
Fixes #39754
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Related issues
Logs
Heartbeat on arm64: