Skip to content
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

Handle remaining new grammar features (string count in range, string set in range and rule sets). #46

Merged
merged 3 commits into from
Dec 20, 2021

Conversation

wxsBSD
Copy link
Contributor

@wxsBSD wxsBSD commented Dec 14, 2021

Add support for parsing string counts in range: #s0 in (0..100) == 2

Add support for parsing string counts in range: #s0 in (0..100) == 2
Add support for parsing string sets in range: any of ($s*) in (0..100)
@wxsBSD
Copy link
Contributor Author

wxsBSD commented Dec 14, 2021

I updated this to handle both string count in range $a in (0..100) == 2 and string set in range any of $(a*) in (0..100). AFAIK these are the only two currently outstanding features in the YARA language which are left to support in gyp.

If rule sets make it in to the language I will add support for them to gyp too.

To avoid a name clash with RuleSet in the protobuf I called it a
RuleEnumeration.
@wxsBSD
Copy link
Contributor Author

wxsBSD commented Dec 17, 2021

Added support for rule sets (I had to call them RuleEnumeration in the protobuf to avoid a name clash) on the assumption they will be in the next release. If they aren't I'll be happy to back out this change and we can deal with it later.

@wxsBSD wxsBSD changed the title Handle string count in range. Handle remaining new grammar features (string count in range, string set in range and rule sets). Dec 17, 2021
@plusvic plusvic merged commit dcbdccd into VirusTotal:master Dec 20, 2021
@wxsBSD wxsBSD deleted the new_grammar_features_2 branch December 20, 2021 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants