ROX-30257: implement permission change tracking #157
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.
Description
This is done via the path_chmod LSM hook, extending the existing event structure to allow for additional, event type specific information to be sent to userspace.
Changes in userspace are relatively straightforward, the received event is translated into a new
ChmodFileDatatype that wraps the more genericBaseFileDataand adds fields specific for permission changes.Fromtraits are implemented for translation between this type and the gRPC protobuf messages.Checklist
Automated testing
If any of these don't apply, please comment below.
Testing Performed
The existing bpf unit test has been extended with a permission change event in order to exercise the new bpf program.
Integration tests have been added for the new permission change events.