Feature request - Add file.capabilities (Linux) #1020
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
titouanj added a commit to alumet-dev/packaging that referenced this pull request Apr 16, 2025
Using the command function for the moment. Will use the capabiliy one when goss-org/goss#1020 is merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
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.
Checklist
make test-all(UNIX) passes. CI will also test thisDescription of change
This is a new test feature included in
filetest calledcapabilities.It aims to add a simple way to test for file Linux effective capabilities .
The test uses this Golang package https://github.com/syndtr/gocapability .
Usage:
It will test if the file has the capabilities
CAP_PERFMONandCAP_SYS_ADMIN, if not the test fails.One problem with that is to use the
enumsyntax to describe capabilities (see caps enums). I think it would be easier for user to write the name of the capability instead of a number but it requires to add code to transform enum in string, so I was not sure about it in term of code simplicity.This PR is related to this issue #971 .
📚 Documentation preview 📚: https://goss--1020.org.readthedocs.build/en/1020/