Closed Azathothas closed 1 year ago
Thanks for your question. The reason you're seeing this behavior is because modules can only be enabled/disabled via the command line. The config is mainly for changing their individual options. (Internal modules, e.g. excavate and speculate, are the exception. They are essential to most scans and are enabled by default, but in edge cases they can be disabled via the config).
Flags are groups of modules. With -f subdomain-enum
, you're enabling every module with the subdomain-enum
flag. (You can list these with bbot -l -f subdomain-enum
).
To disable individual modules, you can specify -em massdns ...
. You can also exclude by flag, e.g. -ef slow
.
I have a custom config file where I have enabled only certain modules. Command:
Config file:
As you can see:
dns_resolution: false
massdns
anywhere inmodules
Expected Behaviour:
config file
or via-m
, but it runs other modules that are initiated by -fsubdomain-enum
but it's running
massdns
anywayAm I doing the config file configuration the wrong way? if so, what would be the setting to disable/enable certain modules ?