Closed s4chin closed 6 years ago
Thanks, that sounds promising! Is it also possible to add module-specific command line arguments to exitmap's configuration file? For example, .exitmaprc could have the following content:
[Defaults]
verbosity = info
build_delay = 0.3
analysis_dir = /tmp/exitmap_scans
Thanks for your work, Sachin! Is this ready for review now?
Okay, this is ready for review. Changes:
args
are passed to the setup()
function of the modules, so the setup()
function can be modified to handle the sub-arguments../bin/exitmap -h
prints out help about exitmap with also the available module names../bin/exitmap module -h
prints out help about the specific module.I haven't implemented any sub-commands yet, but they can be easily done once the sub-command lists for modules have been decided.
This approach is the second approach.
exitmap -h
prints out the help for exitmap, andexitmap module -h
prints the help for the modules. So now exitmap works asexitmap module
, for example if one wants to rundnspoison
andchecktest
, one has to type two commands:The con is that when a new module is added(as you recently did), the subparser code has to be modified so those modules can be used. But the code is a single line so I don't think it should be an issue. Should I continue with this approach?