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

..

browser

check for ssl related errors. Fix #993

2016-09-05 22:58:56 +02:00

collections

Add passive detection of google-universal-analytics

2016-10-14 14:48:48 +02:00

models

Preciser reporting in bruteforcing password with bad response

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

plugins

License text removed from sources, see the LICENSE file

2013-04-05 14:06:31 +02:00

browser.rb

check for ssl related errors. Fix #993

2016-09-05 22:58:56 +02:00

cache_file_store.rb

drop ruby 1.9 support, whitespaces

2016-02-23 18:07:20 +01:00

common_helper.rb

make wpscan ruby 2.4.0 compatible

2017-01-17 20:24:32 +01:00

custom_option_parser.rb

License text removed from sources, see the LICENSE file

2013-04-05 14:06:31 +02:00

db_updater.rb

remove cloudflare error handling

2016-11-01 19:38:47 +01:00

errors.rb

remove cloudflare error handling

2016-11-01 19:38:47 +01:00

hacks.rb

make wpscan ruby 2.4.0 compatible

2017-01-17 20:24:32 +01:00

typhoeus_cache.rb

Proper fix for #429

2014-03-21 09:50:57 +01:00

version_compare.rb

Implement lesser? method #862

2015-09-08 17:54:32 +02:00