Adding support to use json file to use only specific plugins

[xmco]

TLTR

This merge request adds a new feature to use a Json file to use only specific plugins --plugins-conf or -p.

Usecase

If you are scanning for a specific port, you don’t necessarily need to load all the plugins. Therefore, we added a new option to set a specific set of plugins. The default value is plugins.json which is located in the current directory. The format for the file is simple, only the name of the plugins is needed :

{
  "plugins": [
    "CouchDbOpenPlugin",
    "ElasticSearchExplorePlugin",
    "ElasticSearchOpenPlugin",
    "MongoSchemaPlugin",
    "MongoOpenPlugin",
    "SSHOpenPlugin",
    "DotDsStoreOpenPlugin",
    "NucleiPlugin",
    "MysqlOpenPlugin",
    "MysqlExplorePlugin",
    "RedisOpenPlugin",
    "KafkaOpenPlugin",
    "ApacheStatusHttpPlugin",
    "ConfigJsonHttp",
    "DotEnvConfigPlugin",
    "GitConfigPlugin",
    "IdxConfigPlugin",
    "LaravelTelescopeHttpPlugin",
    "PhpInfoHttpPlugin",
    "FirebaseHttpPlugin",
    "WpUserEnumHttp"
  ]
}

[gboddin]

Hi, not forgetting about this !

This is interesting, I will probably extend it with plugin configuration so we can finally pass settings to them ( options part of https://github.com/LeakIX/l9format/blob/master/l9plugin.go#L98 )

Probably with include exclude and protocols section with plugins as a list.