From 248942bdeafe1bb1519d51fde4a80b52776f179a Mon Sep 17 00:00:00 2001 From: Erwan Date: Wed, 11 Sep 2019 11:29:45 +0200 Subject: [PATCH] Updates Readme (adds link, fixes typo) --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index dff90e57..268613c2 100644 --- a/README.md +++ b/README.md @@ -84,6 +84,8 @@ For more options, open a terminal and type ```wpscan --help``` (if you built wps The DB is located at ~/.wpscan/db +## Load CLI options from file/s + WPScan can load all options (including the --url) from configuration files, the following locations are checked (order: first to last): - ~/.wpscan/scan.json @@ -113,11 +115,13 @@ cli_options: Running ```wpscan``` in the current directory (pwd), is the same as ```wpscan -v --proxy socks5://127.0.0.1:9090 --url http://target.tld``` -Such feature is useful to keep the API Token in a config file and not have to supply it via the CLI each time. To do so, create the ~/.wpscan/scan.yml file containing the below: +## Save API Token in a file + +The feature mentioned above is useful to keep the API Token in a config file and not have to supply it via the CLI each time. To do so, create the ~/.wpscan/scan.yml file containing the below: ```yml cli_options: - api_token: YOuR_API_TOKEN + api_token: YOUR_API_TOKEN ``` Enumerating usernames