You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I wanted to disable S14 module in module_blacklist.txt file and I used the default-scan.emba profile for testing and the S14 was running.
The module dependency is a complex thing and sometimes a scan is stucked with a module for days. In this case I would like to repeat it without the never ending modul but module_blacklist.txt and default-scan.emba profile looks like do not work together.
Describe the bug
I wanted to disable S14 module in module_blacklist.txt file and I used the default-scan.emba profile for testing and the S14 was running.
The module dependency is a complex thing and sometimes a scan is stucked with a module for days. In this case I would like to repeat it without the never ending modul but module_blacklist.txt and default-scan.emba profile looks like do not work together.
To Reproduce
Steps to reproduce the behavior:
EMBA installation (dev-mode/default mode)
Use the firmware available here: https://github.com/dougcooper/kankun/blob/master/kkeps-3.5.bin
Start EMBA with the following parameters: $ sudo ./emba -l ~/Kankun -f ~/kkeps.bin -p ./scan-profiles/default-scan.emba -X 1.0 -Y Kankun -Z SmartPlug -N kkeps.bin
add S14 to module_blacklist.txt before test run:)
Check S14 test report.
Expected behavior
In general a module dependency chart would be nice for the future.
The blacklist config file should be valid with each profile.
Screenshots
Desktop (please complete the following information):
Priority issue
Are you already a Sponsor? - [N]
The text was updated successfully, but these errors were encountered: