New db structure - Allowing to detect crypto constants in the code

[pawlos]

This is first proposal to fix the issue in #7.

The change consists of:

• extending the DB by additional field with the size of crypto constant sub-element
• Ghidra script first tries to search for the whole constant and only if it is unable to find it goes to the second mode
  • it starts to search for parts of constant based on the size of each element. To limit the amount of searches it does it up to 20 sub-elements.
  • the decision whether a constant is considered found or not is based on how many of those sub-elements were found; current threshold is set to 0.8

Benefits:

• more crypto consts found, when "hidden" in code
• works in headless mode

Drawbacks:

• increased search time

Only tested on 3 binaries that I got some problems with the original script. It would be nice to test on more cases before the merge. Fixes #7.

[pawlos]

Feel free to suggests any improvements and/or changes.

[d3v1l401]

I have a few jobs to do involving crypto binary searching, I'll test this in action before merging ;) I'll let you know more.

[d3v1l401]

I fixed a wrong constant name within the script (DETECTION_THRESHOLD) and setted up the script for update.

Merged.