Comments (7)
Even if this feature is implemented it won't apply to version 1.6 and lower. I
mean, in version 1.7 you will be able to ignore new syntax included in version
1.8, but version 1.6 and lower will fail anyway.
Could you explain a little more your real-life situation where this feature is
needed? Why not keeping your YARA version up to date?
Original comment by [email protected]
on 11 May 2012 at 12:25
from yara-project.
Sure, I'd be happy to provide more detail:
Assume you have 1,000's of "systems" all with YARA installed. Do you really
think its realistic that you should have to "upgrade" those instances of YARA,
simultaneously? If you have a directory containing your "master YARA rule
list" that is being replicated out to each of these systems, before you upgrade
_any_ of those rules to leverage new features, you have to make sure that all
versions of YARA across all 1000 systems are updated, accordingly. Currently,
to get around this, you'd have to externally maintain different "versions" of
the "master list" for each version of YARA, which makes overall rule management
more painful than it needs to be.
Yes, if v1.7 started implementing this feature, you would still have to deal
with this painful setup at least until all your systems are upgraded to v1.7.
But, once that happens, when v1.8 and later is released, the process becomes
much more manageable.
Lastly, if you're accepting YARA rules for a third-party, having an option to
require min_version on each rule makes it easier to perform initial rule
_validation_ back to that third-party. For example, if you're running YARA
v1.4 and the third-party uploads v1.6 YARA rules, we can have YARA output an
explicit "unsupported version" error message, rather than vague syntax errors,
which we then have to decipher and translate as "unsupported version",
accordingly.
Does this make sense?
Original comment by [email protected]
on 11 May 2012 at 2:09
from yara-project.
To clarify further, if YARA v1.7 implemented the "min_version" meta tag, you
could then provide a command-line options like:
--enforce_version
If (--enforce_version) were present, YARA would explicitly generate errors if
it encountered any rule with min_version _higher_ than its current version.
If (--enforce_version) were NOT present, then YARA would _silently_ ignore any
rules where min_version is _higher_ than its current version.
Original comment by [email protected]
on 11 May 2012 at 2:13
from yara-project.
Ok, I see your point. But I think, I would prefer some kind of preprocesor
directives in the style of the C language. For example:
#if yara_version >= 1.7
some rules here using new features available in 1.7
#endif
That would be more flexible. What do you think?
Original comment by [email protected]
on 11 May 2012 at 11:05
from yara-project.
Sure, that makes complete sense. Thanks for your time!
Original comment by [email protected]
on 12 May 2012 at 12:08
from yara-project.
This will be solved with a C-style preprocessor with conditionals. See issue 61.
Original comment by [email protected]
on 15 Aug 2012 at 4:11
from yara-project.
Original comment by [email protected]
on 15 Aug 2012 at 4:12
- Changed state: WontFix
from yara-project.
Related Issues (20)
- variable in range using the offset of another variable as last parameter in range will hit even if the second variable does not exists HOT 1
- malfind and yara (volatility 2.2) HOT 1
- Yara-Python DLL Load Failure HOT 3
- RegEx no longer greedy in v1.7 HOT 1
- /usr/bin/ld: error: cannot find -lyara HOT 4
- Infinite loop on certain samples with one particular rule. Regex related. HOT 1
- Fix abort issue on ARM platforms HOT 1
- [yara python]match() method does not accept variable as parameter HOT 1
- Old issue closed but not fixed HOT 1
- Python - read access during match is not read only HOT 1
- Buffer overflow
- latest svn with gcc 4.7.1 build issue HOT 1
- trying to build python-yara 1.7
- yara 1.7 gets stuck. HOT 2
- YARA 1.7 failing to detect a one-byte string at the end of a two-bytes file
- Failure to build on trunk on ubuntu 12.04 x86_64 HOT 2
- yara-python fails to build on OS X 10.8.5 HOT 1
- Uppercase or Lowercase HOT 2
- Unable to compile Yara on OS X HOT 10
- Yara rule working in 2.0 but not in yara 1.6 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from yara-project.