We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Global rules with string matches do not seem to behave properly anymore, and even if they do not match, normal rules that match are returned.
Steps to reproduce the behavior:
with this file:
global rule g1 { strings: $ = "g1" condition: all of them } rule foo { strings: $ = "foo" condition: all of them }
and an input foo, the foo rule is reported as matching, but should not, since the global rule did not match.
foo
yara 4.3.1 does not have the bug, not does yara 4.4.0, but master has it.
Bisecting seems to indicate this commit introduced the regression: b26b000
The text was updated successfully, but these errors were encountered:
cddec11
No branches or pull requests
Global rules with string matches do not seem to behave properly anymore, and even if they do not match, normal rules that match are returned.
Steps to reproduce the behavior:
with this file:
and an input
foo
, thefoo
rule is reported as matching, but should not, since the global rule did not match.yara 4.3.1 does not have the bug, not does yara 4.4.0, but master has it.
Bisecting seems to indicate this commit introduced the regression: b26b000
The text was updated successfully, but these errors were encountered: