-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Regression on long hex strings in yarac #688
Comments
@JusticeRage The second error message means that you used |
I can reproduce the error with a hex string describing 3004 or more bytes. |
A critical upstream bug (VirusTotal/yara#688) is still unresolved.
This is because this other issue #674
But I highly discourage the use of such long strings as they are usually unnecessary. A few hundred bytes should be enough, you don't need thousands of bytes for creating a very unique string. |
|
Thanks! I agree completely on the principle,but some of my rules are generated automatically from external sources, so I don't have full control over their quality. |
Hi! I've recently upgraded to Yara 3.6 (latest master revision) and I'm hitting errors with previously functional rules.
Here is the first one:
I tried reducing the test case, but if I delete any more bytes, I get the following error:
Upon further inspection, it seems that this issue only happens when the hexadecimal string is very long.
There also seems to be new rules rejected because the "regular expression is too complex". That didn't happen before, can you comment on this?
Finally,is there a way to compile the rules anyway by ignoring the ones that cause an error?
Thanks!
The text was updated successfully, but these errors were encountered: