Binja database support

[xusheng6]

This PR adds support for loading and analyzing a binja database: #2496

There are two things I wish to mention:

1. This PR is rebased on Various binja backend fixes #2500, rather then the latest master. I now realize this is not the best thing to do, but I cannot simply drop the commits from Various binja backend fixes #2500 because there are conflicts. So maybe first have a look at that PR, and if it gets approved, I can rebase this again (if needed)
2. I did not add a unit test for this. I know I can save one of the file we use for unit tests to a binja database and then load it. Do you have a representative binary to use for it among those files? Also, should I add a new test or should I just add it to test_binja_features.py?

Checklist

• No CHANGELOG update needed

• No new tests needed

• No documentation update needed

[williballenthin]

Do you have a representative binary to use for it among those files? Also, should I add a new test or should I just add it to test_binja_features.py?

I think you should take a trivial file, like PMA 01-01.dll, and use that. The test only needs to show that the db file can be analyzed, not that all the features are extracted consistently (which we can assume will be the case, I think).

[williballenthin]

good catch

[mr-tz]

Pending tests

[xusheng6]

Pending tests

I added a test for for it, please have a look!

[xusheng6]

Oh well apparently I only added the database file and the feature list, but forgot to make it actually run during the test. I will push a fix shortly

[mr-tz]

Great, thank you!

[xusheng6]

Just so that you know this branch is failing the (newly added) unit test (sorry I wrote the code without running the unit test, I thought it is way to easy to bother with testing at all)

All new binja db tests are failing because it cannot properly get a binary view, I am yet to see what is happening. It does work perfectly fine when I analyze a standalone file outside of the unit test infra

[xusheng6]

@williballenthin oh well it is just a simple typo in the file path. I have fixed it and this should be ready for merge

[mr-tz]

Thank you!

[xusheng6]

@mr-tz thx for merging this! However, since I also introduced a submodule change on the test files, now the capa repo points to this commit https://github.com/mandiant/capa-testfiles/tree/b40457c616604ee65f44e1ae8597cfeec7da0f70 which is not on top of the master branch of the capa-testfiles repo. I believe you should cherry-pick this commit on capa-testfiles

[mr-tz]

Good catch, done. Thank you!