New Kali Linux 2024.01 available
m-1-k-3 opened this issue · 10 comments
New Kali Linux is out: https://www.kali.org/blog/kali-linux-2024-1-release/
We need to test EMBA on it
Testcases:
Testfirmware: DLink DIR300
- Default/docker installation working with current docker image
-
./installer.sh -d
finished without errors - dependency check (
./emba -d 1
) - EMBA run with profile quick-scan
- 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)
-
- Docker base image build
-
sudo docker-compose build --no-cache --pull
finished without errors - dependency check (
./emba -d 2
) - EMBA run with profile quick-scan
- 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 on Kali Linux
-
./installer.sh -F
finished without errors - dependency check (
./emba -d 1
) - 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
-
Kali 2024.1
./emba -d 1
ERROR:
GHIDRA - not ok
Missing GHIDRA - check your installation
CHECK:
apt install ghidra
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ghidra is already the newest version (11.0+ds-0kali1).
ERROR:
Looks like your docker container is outdated - please update your base image: sudo docker pull embeddedanalyzer/emba'.
ERROR: 1
CHECK:
sudo docker pull embeddedanalyzer/emba
Using default tag: latest
latest: Pulling from embeddedanalyzer/emba
Digest: sha256:eb64476d7e42d1a101bd041dd9a48fd0c9f314195214ceb6f73def86a51d8108
Status: Image is up to date for embeddedanalyzer/emba:latest
docker.io/embeddedanalyzer/emba:latest
i get this 2 errors which are false.
- Have you checked out the latest state of the EMBA repo?
- installed EMBA via sudo ./installer.sh -d?
- then the dependency check should not fail
used ./installer.sh -d for installation
used the 1.3.2 zip and not latest repo
OK. We are right before the next release. Please use the latest GitHub version for testing.
cool ... full install is always the most challenging as it is nearly not tested in between the releases ... looking forward to the results