[RFC] Add support for gen_system_context #299
Draft
Conversation
This file contains 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
|
What does use this? Is this macro in some open-source policy? Also, it looks like you didn't include the fixes to #298 on this branch, so it will need a rebase. |
Support a wrapper for `gen_context(system_u:object_r:CTX, s0)` named `gen_system_context(CTX)`. Support it as alternative to gen_context() in .te via the parser and in .fc files via extending the custom_fc_macros search logic.
cgzones
force-pushed
the
gen_system_context
branch
from
55be2f4 to
a458cba
Compare
|
@cgzones ping on the above question
Just trying to understand the motivation for supporting this macro, since I've never heard of this particular macro. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Support a wrapper for
gen_context(system_u:object_r:CTX, s0)namedgen_system_context(CTX).Support it as alternative to gen_context() in .te via the parser and in .fc files via extending the custom_fc_macros search logic.
I am not sure whether it's worth to have something non-reference style specific like this in SELint though.
Depends on #298.