34 Commits

Author SHA1 Message Date
FusionPBX
1a95aeb331 Fail2ban - Fix the delimitter for the port range in jail.local. 2017-11-29 22:26:02 -07:00
FusionPBX
21512467a7 Update jail.local 2017-11-29 19:43:52 -07:00
FusionPBX
fe95015dc7 Update jail.local 2017-11-28 23:02:20 -07:00
FusionPBX
78875548ae Update jail.local 2017-11-28 22:52:03 -07:00
FusionPBX
37ecd268db Update jail.local 2017-10-09 11:33:17 -06:00
FusionPBX
609ae00d86 Rename fusionpbx-invalid-mac.conf to fusionpbx-mac.conf 2017-10-09 11:32:37 -06:00
FusionPBX
98e1afe8fe Update jail.local 2017-10-08 23:58:24 -06:00
FusionPBX
aa78b22568 Update jail.local 2017-10-08 23:49:05 -06:00
FusionPBX
f91c4d3fb6 Update jail.local 2017-10-08 23:24:23 -06:00
FusionPBX
f78137a767 Create fusionpbx-invalid-mac.conf 2017-10-08 22:43:19 -06:00
FusionPBX
b0d9c28ab4 Update jail.local 2017-10-08 22:31:50 -06:00
FusionPBX
d7273a3f5a Update jail.local 2017-10-08 22:29:31 -06:00
emaktech
a33131c8be Ban on auth failure instead of challenge (#113)
Default fail2ban DoS ruleset looks for auth challenges, but auth challenges can be either successful or unsuccessful. Default rule causes problems with larger environments with many registered devices as they have many successful auth challenges with short registration periods.

By the time auth challenges can be made successfully in volume, it's far too late to be worrying about a DoS or brute force attempt - it's already too late. Rule change here will reduce false positives while still providing same level of useful protection.

Maybe also consider reducing maxretry count or increasing findtime in jail.local to catch true failed auth brute force or DoS attempts more easily in conjunction with above change.

This will be more sensitive in detection and should carry lower false positive rate.
2017-09-02 09:09:07 -06:00
FusionPBX
db6815d315 Update jail.local 2017-06-06 23:15:08 -06:00
root
16451807dd update the file permissions 2017-03-05 06:11:42 +00:00
FusionPBX
e9a1ed3038 jail.local disable the ip ban by default
I think this is stopping beginners. Easy to enable.
2017-01-15 00:54:59 -07:00
FusionPBX
922677a65e Update jail.local 2016-11-25 22:00:58 -07:00
FusionPBX
2e042cf201 Rename freeswitch-inbound.conf to freeswitch-404.conf 2016-11-25 21:30:15 -07:00
FusionPBX
82efcb30d6 Update jail.local 2016-11-25 21:27:24 -07:00
FusionPBX
ce06e5d79c Update jail.local 2016-11-25 18:16:08 -07:00
FusionPBX
2d0357b1b4 Rename freeswitch-404.conf to freeswitch-inbound.conf 2016-11-25 18:13:49 -07:00
FusionPBX
cbe27f0e88 Create freeswitch-404.conf
Fail2ban add inbound routes 404 not found
2016-11-25 18:10:50 -07:00
FusionPBX
76be73890e Update nginx-404.conf
This will only match 404 results, not 404 bytes.
2016-10-26 12:02:48 -06:00
FusionPBX
81d22845b8 Update jail.local 2016-10-26 11:54:02 -06:00
Chris Black
cc3ecea384 nginx-dos should block 443 as well. (#36) 2016-08-23 10:16:15 -06:00
Alexey Melnichuk
3bf249ac43 Fix. Bun IP requests (#25) 2016-06-30 08:13:55 -06:00
DigiDaz
53b9f40b40 Make ban action more reflective of the attack type (#13) 2016-05-28 18:39:14 -06:00
FusionPBX
249b9d74a6 Update jail.local
Set the fail2ban to block only web interface for failed authentication attempts.
2016-05-28 13:01:48 -06:00
Mafoo
bf5a253f65 fixes for fail2ban (#10)
export the command line variables so sub scripts can use them
use sed to update log path is source is used
simplify freeswitch rules to use protocol=all
general tidy up of spacing in files
2016-05-28 12:09:45 -06:00
blackc2004
59516f7708 Add NGINX 404 and DOS filters 2016-05-04 15:58:38 -07:00
FusionPBX
59e5c72f80 Update jail.source 2016-05-04 14:24:24 -06:00
FusionPBX
81b42e420f Update jail.package
Add a new filter for fail2ban - freeswitch-ip
2016-05-04 14:23:17 -06:00
FusionPBX
544f9de6d8 Create freeswitch-ip.conf 2016-05-04 14:20:24 -06:00
markjcrane
5988b7ed7d Add a shell install script. 2016-04-29 13:24:22 -06:00