Firmware diffing preparation

[m-1-k-3]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Feature, Bug fix

• What is the current behavior? (You can also link to an open issue here)

No firmware diffing possibilities

• What is the new behavior (if this is a feature change)? If possible add a screenshot.

This is a preparation PR for the upcoming firmware diffing mechanism
This PR includes multiple bug fixes and introduces the new -o parameter for the upcoming firmware diffing mechanism

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Firmware diffing preparation. Please review the current state and check the functionality and the working of the web report.

[torabi12]

I wanted to try out the FW compare function with this command:

$ sudo ./emba -l ~/GS1200 -f ~/GS1200-5_V1.00ABKM.5C0.bin -t -s -z -W -X V1.00ABKM.5C0 -Y ZyXEL -N GS1200-5 -o ~/GS1200-5_V2.00ABKM.2C0.bin

but the scan stopped at the beginning:

I installed the fw_differ version. Maybe I did not use correctly the parameters?

[m-1-k-3]

@torabi12 this is fine :) The diffing modules are currently not included. This PR is for preparing everything around them and to ensure nothing is broken.

[m-1-k-3]

Started with a wiki entry for the diffing mode here: https://github.com/e-m-b-a/emba/wiki/Firmware-diffing

[BenediktMKuehne]

tests look good

[m-1-k-3]

I wanted to try out the FW compare function with this command:

$ sudo ./emba -l ~/GS1200 -f ~/GS1200-5_V1.00ABKM.5C0.bin -t -s -z -W -X V1.00ABKM.5C0 -Y ZyXEL -N GS1200-5 -o ~/GS1200-5_V2.00ABKM.2C0.bin

but the scan stopped at the beginning:

I installed the fw_differ version. Maybe I did not use correctly the parameters?

Should work now with the current master branch. Feedback welcome :) See also here https://github.com/e-m-b-a/emba/wiki/Firmware-diffing

[torabi12]

I selected a classic router E1200 from Linksys, starting with this command:

$ sudo ./emba -l ~/E1200_diff -f ~/1.0.04.001_US_20120307.bin -o ~/2.0.11.001_US_20180910.bin

I cought the beginning:

and after a few seconds it has finished:

The report is this:
E1200_html_report.tar.gz

Is this what we expect from the comparison?

[m-1-k-3]

Shit ... We need to update our container first

[m-1-k-3]

@torabi12 docker image should be ready. Dep checker should now also check for ssdeep

[torabi12]

I repeated the same test:

End of compare:

Report of the scan:
E1200_diff_report.tar.gz

Maybe I should try with different binaries?

[m-1-k-3]

Firmware differ did a quite good job :)

It looks as there are a lot of changes between these two firmware images:

Extracted files: 506 │
vs
Extracted files: 1475 │