Update Yara to 4.0.1 #769
Merged
Update Yara to 4.0.1 #769
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r_newer rule Looks like the new YARA 4.0.1 ends dotnet user strings only with "\x00" instead of "\x00\x00" as before.
|
run tc tests |
|
run tc tests |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update YARA from 3.11.0 to 4.0.1.
Fix #758 and #283 (4.0.1 contains code from VirusTotal/yara#1272).
Also, Yaracpp is refactored and simplified.
@ladislav-zezula, @metthal, @tamaroth
It seems that the new YARA has slightly different Dotnet strings. I had to modify
eziriz_dotnet_reactor_62_or_newer. In the example we have in regression tests, there is one less Dotnet user string, and these strings are terminated only with\x00- it was\x00\x00before in 3.11.0.See these logs from
yara -D:yara-3.11.0.txt
yara-4.0.1.txt