mir/apparmor
2
0
Fork 0
mirror of https://gitlab.com/apparmor/apparmor synced 2025-08-30 22:05:27 +00:00
Code Issues Releases Wiki Activity

Change the second key_capability entry into a comment and document why

Browse Source 
its there and what to do with it once the old entry types are cleaned up.
This commit is contained in:
John Johansen
2010-09-09 16:51:44 -07:00
parent 073064bdb0
commit 5c43890b31
1 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
libraries/libapparmor/src/scanner.l
View File

@@ -348,7 +348,18 @@ yy_flex_debug = 0;
{key_fsuid} { return(TOK_KEY_FSUID); }
{key_ouid} { return(TOK_KEY_OUID); }
{key_comm} { return(TOK_KEY_COMM); }
{key_capability} { return(TOK_KEY_CAPABILITY); }
/* This key_capability entry is here to document, what should be.
* currently the capability token is handled by the old set of rules above
* it should be handled here, but there is no good way to combine them
* that doesn't require more work than it is worth atm because of the
* switch to sub_id in the old scanner rules.
* The switch to sub_id causes the new rule set in the grammar to need to
* accept a TOK_ID instead of TOK_DIGITS, which it should be.
* once the old rules and old scanning is ripped out this scanner rule
* should be activated and the corresponding rule in the grammar should
* be updated to use TOK_DIGITS
* {key_capability} { return(TOK_KEY_CAPABILITY); }
*/
{key_capname} { return(TOK_KEY_CAPNAME); }
{key_offset} { return(TOK_KEY_OFFSET); }
{key_target} { return(TOK_KEY_TARGET); }