Victor M. Alvarez

Results 206 comments of Victor M. Alvarez

> I haven't looked into it yet, but if possible I think all of this should be done in a library so it can be easily used by other tools....

Introduction of line breaks at appropriate places, specially in the case of rule condition, is a pending improvement too. That's a bit more complicated, it's not a low hanging fruit...

I believe you can achieve what you want with a bit of unsafe code: ```rust /// Wraps a yara_x::Rules, but preventing it from moving around in memory. struct PinnedRules{ rules:...

@qjerome that doesn't work because `yara_x::Scanner` needs a reference to the rules in `MyScanner.rules`, you can create a scanner that receives that reference, but you can't move it into `MyScanner.scanner`.

That information is not currently exposed in the API.

Closing as obsolete.

The `ReadFrom` not only loads the rules from the given reader, it also creates the Aho-Corasick automaton and produces the native code for the current platform. The time is probably...

Try this: ``` cargo build --release --features=logging RUST_LOG=info ./target/release/yr compile big_rule.yar -o big_rule.yarc RUST_LOG=info ./target/release/yr scan -C big_rule.yarc README.md ``` And paste here the logs you get. They should look...

That's strange, can you provide details about operating system, and CPU type?

Can you try the same on Windows without WSL?