50 Shades of YARA
> an overview of the different rule types
> reasons why there is no single best #YARA rule for the detection of a certain malware/tool
https://t.co/vvficebfuy
@James_inthe_box@bry_campbell "C:\Users\Admin\Documents\Visual Studio 2015\Projects From Ryuk\ConsoleApplication54\x64\Release\ConsoleApplication54.pdb"
@wxs Sure, However, in the cases where I find myself getting this error, it's often because of unbounded regular expressions or too short strings. The later most often leads to false-positives
@wxs Absolutely. Yara warnings should be addressed before the rule is published (just like readability / style requirements / etc). My general rule of thumb is if it triggers a warning, it'll trigger false-positives.
@wxs Interesting. In the case, using things like uint16(0) == 0x5A4D won't really help with performance because it is a check condition check and handled post string searching.
Setting a global rule to restrict scanning files over n-MB or by file-type by using uint16(0) == 0x5A4D (for PE files)? Yara will still scan the file, however, it will not optimize the scan performance (#Malware / #MalwareAnalsis) (Thanks @wxs )