Zaur 338eacd63b Preciser reporting in bruteforcing password with bad response ...

When bruteforcing for multiple logins and passwords the bad response code reported
might indicate a match! But the reporting for it is not clear enough.
For example "Unkown response for admin" might mean a user name admin and some password
or a password 'admin' for some user.

This commit makes in unambiguous reporting a bad response, and naming which login and
which password caused it.

2017-03-25 16:18:05 +01:00

..

vulnerability

Initial attempt at implementing apiv2 #853

2015-08-14 00:19:22 +02:00

wp_item

typo

2016-05-31 14:53:50 +02:00

wp_theme

more advanced version detection

2016-05-31 14:51:09 +02:00

wp_timthumb

remove executable flags

2016-05-09 16:19:11 +02:00

wp_user

Preciser reporting in bruteforcing password with bad response

2017-03-25 16:18:05 +01:00

wp_version

fix #974

2016-08-08 21:40:36 +02:00

vulnerability.rb

remove executable flags

2016-05-09 16:19:11 +02:00

wp_item.rb

fix typo

2017-01-28 00:40:51 +01:00

wp_plugin.rb

remove executable flags

2016-05-09 16:19:11 +02:00

wp_theme.rb

remove executable flags

2016-05-09 16:19:11 +02:00

wp_timthumb.rb

remove executable flags

2016-05-09 16:19:11 +02:00

wp_user.rb

remove executable flags

2016-05-09 16:19:11 +02:00

wp_version.rb

fix #943

2016-05-13 21:23:22 +02:00