rhardy613 890a3dcbb9 Fix ASSP filter to work with current release of ASSP ... ASSP V1 development stopped at the end of 2014 and it is now deprecated. All users were urged to upgrade to ASSP V2 which is still actively developed. For some reason fail2ban 0.9.5 (and trunk) still have code which only understands ASSP V1 logs. This means the filter ignores brute force attacks against ASSP. Now updated with anchored patterns tested against 6 months of log data.		2016-08-05 17:26:47 -04:00
..
client	fail2ban-regex: extended with option '--raw' (switch to raw host, prevent resolving of ip)	2016-05-30 14:08:37 +02:00
server	amend for new option of usedns=raw - forgotten validation fix inside setUseDns	2016-05-31 17:45:44 +02:00
tests	Fix ASSP filter to work with current release of ASSP	2016-08-05 17:26:47 -04:00
__init__.py	Fix PEP8 E302 expected 2 blank lines, found X	2015-07-04 13:47:40 -04:00
exceptions.py	Fix PEP8 E302 expected 2 blank lines, found X	2015-07-04 13:47:40 -04:00
helpers.py	splitwords: prevent to split to empty values by multiple separator characters together	2016-05-23 15:33:45 +02:00
protocol.py	renamed <NAME> to correct <ACT> in protocol	2015-08-02 14:55:38 +02:00
version.py	DOC: preparations for 0.9.5 release	2016-07-14 21:35:49 -04:00