capa can't be used as a library on py3

[williballenthin]

capa relies on vivisect for its standalone code analysis (when run within IDA, it uses IDA's analysis). since vivisect is py2-only, this means capa is py2-only, when used standalone or as a library. we should provide an analysis backend that can be used on py3, as this is the future.

we're aware that everyone (actually, including ourselves) has already moved on to py3. you should be aware that using vivisect was the path of least resistance to developing capa. now that we've proved that capa works and is useful, its finally appropriate to dedicate substantial time towards the upgrade.

note, the capa code base is already py3 compatible. this is strictly a limitation of the backend that we ship by default.

[williballenthin]

based on offline discussions with @rakuy0, the vivisect devs are working towards py3 support. but, i'd expect this to be many months before its stable.

[williballenthin]

in #234 we have an experimental backend that runs on py3. however, its a pretty new analysis engine, so we're not ready to merge and distribute it yet.

[williballenthin]

we (including @Ana06) may attempt a miasm backend that would support py3. some things would be pretty straightforward (e.g. disassembling instructions) while other things would need a bit of research and code (e.g. finding functions). ETA for a POC is probably a few weeks to a few months. if it works, then further ETA for stabilizing this depends on performance and reliability.

we're certainly open to collaboration on this effort, if anyone is interested.

TODO: update with GH issue # if we attempt miasm backend.

[mbhatt1]

How do the tests look currently for #234 ?

Are the preliminary results fairly ok for most runs?

[williballenthin]

@mbhatt1 tests look good

with this backend, you're more likely to run into errors during the code analysis passes, since the analyzer hasn't yet been hardened against thousands of binaries. this would look like unexpected exceptions and/or missing results. but, the interface can be used from py3 and is unlikely to change too much (though not guaranteed). so, you could get started here and sketch out your integration.

[williballenthin]

see also #355 that uses SMDA for py3

[williballenthin]

with SMDA added, capa can be used as a library on py3.