-
Notifications
You must be signed in to change notification settings - Fork 897
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
Find-and-replace does substitution in list names #197
Comments
I see, you're right. The substitution I do for list names is pretty naive. I'll modify it to be list item/whitespace aware. |
mstemm
added a commit
that referenced
this issue
Feb 24, 2018
Start tracking whether or not a given macro/list is actually used when compiling the set of rules. Every macro/list has an attribute used, which defaults to false and is set to true whenever it is referred to in a macro/rule/list. When run with -v, any macro/list that still has used=false results in a warning message. Also, it turns out the fix for #197 wasn't being applied to macros. Fix that.
mstemm
added a commit
that referenced
this issue
Feb 26, 2018
Start tracking whether or not a given macro/list is actually used when compiling the set of rules. Every macro/list has an attribute used, which defaults to false and is set to true whenever it is referred to in a macro/rule/list. When run with -v, any macro/list that still has used=false results in a warning message. Also, it turns out the fix for #197 wasn't being applied to macros. Fix that.
mstemm
added a commit
that referenced
this issue
Feb 26, 2018
Start tracking whether or not a given macro/list is actually used when compiling the set of rules. Every macro/list has an attribute used, which defaults to false and is set to true whenever it is referred to in a macro/rule/list. When run with -v, any macro/list that still has used=false results in a warning message. Also, it turns out the fix for #197 wasn't being applied to macros. Fix that.
mstemm
added a commit
that referenced
this issue
Feb 26, 2018
* Add the ability to validate multiple rules files Allow multiple -V arguments just as we do with multiple -r arguments. * With verbose output, print dangling macros/lists Start tracking whether or not a given macro/list is actually used when compiling the set of rules. Every macro/list has an attribute used, which defaults to false and is set to true whenever it is referred to in a macro/rule/list. When run with -v, any macro/list that still has used=false results in a warning message. Also, it turns out the fix for #197 wasn't being applied to macros. Fix that.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like Falco will substitute in the contents of a list into the title of another list if one list contains the name of another.
I discovered this trying to augment the list of known shell spawn binaries. If the lists and rule below are run,
less
andchef-solo
both trigger the "Run shell untrusted" rule. I ended up with some incorrect syntax trying to fix the problem and discovered the substitution in the error below. If the first list is renamed tops_shell_spawn_binaries
, the issue is resolved and the rule doesn't trigger onless
orchef-solo
.The text was updated successfully, but these errors were encountered: