Kali Linux 2022.4 tests

[m-1-k-3]

New Kali Linux is out: https://www.kali.org/blog/kali-linux-2022-4-release/
We need to test EMBA on it

Testcases:

• Default/docker installation working with current docker image (./installer.sh -d)
  • dependency check (./emba.sh -d)
  • EMBA run with profile default-scan in strict mode (-S)
  • EMBA run with profile default-scan-emulation in strict mode (-S)
  • EMBA run with profile full-scan in strict mode (-S)
• Full installation working (./installer.sh -F)
  • dependency check (./emba.sh -d)
  • EMBA run in dev mode with options -s -z -S -D -E -t -W -Q
  • EMBA run in dev mode with options -s -z -S -D, -c, -E, -t, -W -Q
• Docker build (sudo docker-compose build --no-cache --pull)
  • dependency check (./emba.sh -d)
  • EMBA run with profile default-scan in strict mode (-S)
  • EMBA run with profile default-scan-emulation in strict mode (-S)
  • EMBA run with profile full-scan in strict mode (-S)

[torabi12]

If I can take part I would do the first scenario, default docker install of EMBA and 2 tests on the latest Kali.

[m-1-k-3]

If I can take part I would do the first scenario, default docker install of EMBA and 2 tests on the latest Kali.

For sure. Could you please use a "known good" firmware which is working with Kali 2022.3.

[torabi12]

Installation dropped only the issue #427 2 times.

I used for testing the DVRFv0.3 binary file.

Starting command for 1st test was:
$ sudo ./emba.sh -l ~/DVRF -f ~/DVRF_v03.bin -p ./scan-profiles/default-scan.emba -S -X "v0.3" -Y "DVRF" -Z "Router" -N "DVRF_v03.bin"

and at the end:

Report looks good and the scan was also OK.
If you have any suggestions on what I should pay more attention to, please let me know. The second test will be soon.

[m-1-k-3]

Thank you for the test. I will check the package versions next week more in detail.

[torabi12]

So far I've run few emulation firmware tests and I only have one binary to run this with emba. I used this

Starting command:
$ sudo ./emba.sh -l ~/WNAP -f ~/WNAP320_V3.7.11.4.zip -p ./scan-profiles/default-scan-emulation.emba -S -X "V.3.7.11.4" -Y "Netgear" -Z "WNAP320" -N "WNAP_V3.7.11.4.zip"

Ended like this:

I had only this at the beginning:

I added a not existing log folder into the command, I don't know why this question came up.

Report was also nice:

[m-1-k-3]

The logs directory in the EMBA root directory is probably from a EMBA run without the log parameter -l. If you start EMBA without a log directory it automatically generates the default one. I have seen that also ./emba.sh -d creates such a log directory. So, this is a bug. Thank you.

[torabi12]

Yes I made a mistake, at the very beginning I entered the emba.sh command without -l -f parameters and after I executed the full command.

[torabi12]

I checked the full installation mode and it stopped at this point:

and got back the prompt.

[m-1-k-3]

could you please show me the output of the following command:

ls -ld /home/kali/emba/external/*

[torabi12]

The folder looks like this:

[m-1-k-3]

This looks correct. Currently I'm setting up another kali for further testing. First issues are already addressed with #429 and #428

[torabi12]

I tried the installation 2 times and I got the same:

Thank you!

[m-1-k-3]

I tried the installation 2 times and I got the same:

Got it also. I will take a look at it

[torabi12]

I checked again the full installation recently and it stopped with the same error like above:

Stack Trace:
[1] IP12_avm_freetz_ng_extract(): ./installer/IP12_avm_freetz_ng_extract.sh, line 86 -> IP12_avm_freetz_ng_extract
[2] main(): ./installer.sh, line 259 -> main -F

[m-1-k-3]

Uploaded an updated docker image. Please check it out.

[m-1-k-3]

The full installation is not fixed yet. The docker image is used in default installation mode.

[torabi12]

The default installation has been working for me for the last few days, so I thought it was worth trying the full one.
I have just installed a default one but found no difference in the process.

The red lines were there:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
pyppeteer 1.0.1 requires pyee<9.0.0,>=8.1.0, but you have pyee 9.0.4 which is incompatible.
ospd-openvas 22.4.0 requires packaging<21.0,>=20.4, but you have packaging 21.3 which is incompatible.
ospd-openvas 22.4.0 requires paho-mqtt<2.0.0,>=1.6.0, but you have paho-mqtt 1.5.1 which is incompatible.

If you can help me with what to check, I'll try.

[m-1-k-3]

Is on the todo list

[m-1-k-3]

I checked again the full installation recently and it stopped with the same error like above:

Stack Trace: [1] IP12_avm_freetz_ng_extract(): ./installer/IP12_avm_freetz_ng_extract.sh, line 86 -> IP12_avm_freetz_ng_extract [2] main(): ./installer.sh, line 259 -> main -F

addressed with #433

[torabi12]

I tried the full installation and the process stopped like before:

I used a brand new Kali 2022.4 with
$ sudo ./installer.sh -F

I cloned the emba after the #433 merge to main.
If you need more info the system is still running in this state.

[m-1-k-3]

seen it also ... we are going to check this

[m-1-k-3]

update is out there ...

[torabi12]

The full installation went through the previous step but it stopped here on my side: