GithubHelp home page GithubHelp logo

Comments (6)

GoogleCodeExporter avatar GoogleCodeExporter commented on June 15, 2024
I think i'm understanding what you're asking for, but could you give an example 
of something that you would like to express using this feature. I don't find 
any situation that can't be expressed with  "$string at expression" or "$string 
in (expression..expresson)"


Original comment by [email protected] on 13 Jan 2011 at 5:47

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

from yara-project.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 15, 2024
I found a situation where the proposed feature would be more natural than the 
current solution. For example if you want to guarantee that every occurrence of 
some string is inside a given offset range you could say:

for all ocurrence of $string: (@ > expression1 and @ < expression2)

That should be expressed now as:

not $string in (0..expression1) and not $string in (expression2..filesize)

It works, but is not very readable.


Original comment by [email protected] on 13 Jan 2011 at 6:03

from yara-project.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 15, 2024
Thanks for the feedback. Here is an example of what I am trying to express:

rule example
{
  strings:
    $guid = { ... } // 16 bytes

  condition:
    for any of ($guid) : (int32(@ + 16 + x) < 0) // x being some constant/offset
}

I would like the expression to be evaluated for each occurrence of $guid and 
have the rule fire if expression is true for any occurrence in the "for any of" 
case.

Original comment by [email protected] on 13 Jan 2011 at 6:52

from yara-project.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 15, 2024
Interesting, i didn't though about intXX(). People end up using yara in very 
creative ways :)

Well, it makes sense, so i'll try to included in next release.

Original comment by [email protected] on 13 Jan 2011 at 7:04

from yara-project.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 15, 2024
Great! Thank you!

If it would be easier to point me in the right direction, I'd be more than 
happy to take a crack at it.

Cheers.

Original comment by [email protected] on 13 Jan 2011 at 7:15

from yara-project.

GoogleCodeExporter avatar GoogleCodeExporter commented on June 15, 2024
Feature added in version 1.5

Original comment by [email protected] on 22 Mar 2011 at 2:17

  • Changed state: Fixed

from yara-project.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.