-
Notifications
You must be signed in to change notification settings - Fork 165
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
new(libsinsp): add aexepath
, aexe
filter and display option
#938
Conversation
for fields related to proc.x or thread.x Signed-off-by: Melissa Kilby <[email protected]>
Being able to filter process ancestry by exepath can be especially useful for writing rules around shells / RCE originating from java processes, because here often proc.name aka the process name can rather reflect the current program name. This new option provides new opportunities to write filter expressions for many use cases. Signed-off-by: Melissa Kilby <[email protected]>
I like this PR 🚀 ! I think it's a nice useful field to get. I also love the added test and the fact that you're thinking about the field order in the documentation to make it clearer <3 . Nothing against adding that to Also the cleanup makes sense to me, thanks for adding it as an additional commit. |
/milestone 0.11.0 |
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.
Nice PR! I am totally on board with this.
Of course, doing the same for proc.exe
is relevant as well.
Lastly, I agree also on the reordering of these fields in a subsequent PR
Co-authored-by: Luca Guerra <[email protected]> Signed-off-by: Melissa Kilby <[email protected]>
This new option provides new opportunities to write filter expressions for many use cases. Signed-off-by: Melissa Kilby <[email protected]>
aexepath
filter and display optionaexepath
, aexe
filter and display option
Great @LucaGuerra and @loresuso let's discuss best order and perhaps minor adjustments to explanations in the follow up PR. Just added |
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
LGTM label has been added. Git tree hash: 921899869c8ea45d2fa0e0c65286e30d849fb687
|
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.
/approve
TYPE_PEXE, | ||
TYPE_AEXE, | ||
TYPE_PEXEPATH, | ||
TYPE_AEXEPATH, |
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.
next time probably i would add them at the end since we usually do like this
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, incertum, LucaGuerra The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
/kind feature
Any specific area of the project related to this PR?
/area libsinsp
Does this PR require a change in the driver versions?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Being able to filter process ancestry by
exepath
can be especially useful for writing rules around shells / RCE originating from java processes, because here oftenproc.name
aka the process name can rather reflect the program name.This new option provides new opportunities to write filter expressions for many use cases.
Fixes #
Special notes for your reviewer:
proc.exe
for completeness?proc.x
fields slightly so that the end user has a better overview of all supported fields on the website?Does this PR introduce a user-facing change?: