Open winl0gon opened 11 months ago
Hi @marienmare ,
It seems malduck expects the modules to be packages, meaning that the --modules
directory should contain other directories as well, not an __init__.py
on the first level.
In Docker, karton-config-extractor
seems to operate from within the /app/service
working directory and have as default module path extractor/modules
. With the default Docker settings, a valid module would hence be /app/service/extractor/modules/example/__init__.py
. To my understanding, a module placed within the root modules folder (/app/service/extractor/modules/__init__.py
) would fail to load and hence cause YARA to error as no modules were successfully loaded.
PS: The karton-config-extractor
argument syntax seems to be --modules
. I'm not sure the -modules
you mentioned would even be taken into account.
Hope this solves your issue!
I was trying to raise a container using the karton-config-extractor that exists in docker hub.
I've tried
-modules /path/modules/
,-modules /path/modules
,karton-config-extractor -modules /path/modules
,<nothing param>
as arguments to the run command and always get the same error.I think it's probably a problem on the malduck module side, so I leave it here.