OpenKAT scans networks, finds vulnerabilities and creates accessible reports. It integrates the most widely used network tools and scanning software into a modular framework, accesses external databases such as shodan, and combines the information from all these sources into clear reports. It also includes lots of cat hair.
Describe the bug
When a new docker-boefje gets developed, modules of that boefje can get specified inside that boefje's Docker file. But when a module gets added that is not already part of OpenKAT's default python modules, KAT-alogus will throw an error and not include the boefje in the KAT-alogus.
To Reproduce
Steps to reproduce the behavior:
Create a new docker-boefje that uses a module not already used by OpenKAT (for example ssdpy)
run a clean make kat to see everything build successfully.
When you go to the KAT-alogus tab, you will see that your new boefje is not available in the list, and when you look inside the KAT-alogus' logs, errors pop up.
Expected behavior
The boefje should be included in the KAT-alogus because OpenKAT should not require the boefje's dependencies since the boefje will have them installed inside its own docker container.
Screenshots
KAT-alogus' errors:
OpenKAT version
Note the release tag (and if possible: the installation method) here.
If it concerns an in-development version, note the branch(es) and commit hash(es) here as well.
Describe the bug When a new docker-boefje gets developed, modules of that boefje can get specified inside that boefje's Docker file. But when a module gets added that is not already part of OpenKAT's default python modules, KAT-alogus will throw an error and not include the boefje in the KAT-alogus.
To Reproduce Steps to reproduce the behavior:
ssdpy)make katto see everything build successfully.Expected behavior The boefje should be included in the KAT-alogus because OpenKAT should not require the boefje's dependencies since the boefje will have them installed inside its own docker container.
Screenshots KAT-alogus' errors:
OpenKAT version Note the release tag (and if possible: the installation method) here. If it concerns an in-development version, note the branch(es) and commit hash(es) here as well.