Wpscan: output results to file

[digininja]

Pretty simple, have an option to log all output to a file as well/instead of screen. Currently have to pipe through tee to store the results which works but isn't best.

[digininja]

should add, isn't the best as it ends up looking like this

ESC[32m[+]ESC[0m We found 3 themes:

ESC[32m[+]ESC[0m Name: market
| Description:

ESC[32m[+]ESC[0m Name: xxx - v1

[ethicalhack3r]

WPScan should create a log.txt file, this work for you?

[FireFart]

There is a log.txt in your main folder containing the un-colorized output

[digininja]

Two answers here, first, creating that log file without informing the user is going to mean sensitive information could be left lying around, I think automatically creating this is a bad idea.

Having said that, yes, that file does contain what I want. I'd suggest not creating it automatically and instead allowing users to optionally create it with a command line option.

[ethicalhack3r]

I like the idea of optionally creating it

[pvdl]

@digininja
Use the --no-color switch to disable the weird looking escape codes in the plain text output.

[digininja]

Ye but you still have to pipe it or redirect it. Would be nice to just tell
it to save the output.
On 19 Oct 2014 07:29, "Peter" [email protected] wrote:

@digininja https://github.com/digininja
Use the --no-color switch to disable the weird looking escape codes in
the plain text output.

—
Reply to this email directly or view it on GitHub
https://github.com/wpscanteam/wpscan/issues/703#issuecomment-59646891.

[ethicalhack3r]

Logging is now disabled by default and can be enabled with the --log CLI option

[mostafahussein]

is there a way to make --log save report by uri (domain name) instead of the default log.txt ? or in a custom path

[jeffmcjunkin]

For posterity, the command option is now --output / -o, and it disables interactive output to the console.