Commit Graph

454 Commits

Author SHA1 Message Date
FusionPBX f840daa5c6
Update finish.sh 2017-11-29 01:24:10 -07:00
FusionPBX 14f5947b16
Update iptables.sh 2017-11-28 23:10:16 -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 fb03795e44
Update fusionpbx 2017-11-22 20:43:23 -07:00
FusionPBX 424a975098
Update fusionpbx 2017-11-22 19:44:15 -07:00
FusionPBX 87da5733a9
Update node.sh 2017-11-20 22:19:58 -07:00
FusionPBX cc253839b0
Update node.sh 2017-11-20 22:02:08 -07:00
FusionPBX a27eb800be
Create create.sh 2017-11-20 22:00:40 -07:00
FusionPBX df4624b763
Update node.sh 2017-11-20 21:15:22 -07:00
FusionPBX d1b09f6638
Update node.sh 2017-11-20 19:57:09 -07:00
FusionPBX 3afa0c13aa
Update node.sh 2017-11-16 10:06:50 -07:00
FusionPBX c5c55bb35a
Update postgres.sh 2017-11-06 20:54:06 -07:00
FusionPBX d2fd4edcbe
Update postgres.sh 2017-11-06 19:57:35 -07:00
FusionPBX f0e4b5e4c5
Update node.sh 2017-11-06 18:51:52 -07:00
FusionPBX 0237e5fb15
Update node.sh 2017-11-06 18:14:50 -07:00
FusionPBX e448e41f61
Update postgres.sh 2017-11-06 18:11:13 -07:00
FusionPBX 8a1d111aaa
Update node.sh 2017-11-06 18:03:45 -07:00
FusionPBX 04f78936e1
Update postgres.sh 2017-11-06 17:55:38 -07:00
FusionPBX 2fe881b6af
Update config.sh 2017-11-06 17:44:42 -07:00
FusionPBX 151f858c6b
Update fusionpbx 2017-10-31 14:46:31 -06:00
FusionPBX 27bc2f1ab3 Update fail2ban.sh 2017-10-16 16:06:57 -06:00
FusionPBX 41a23cbe81 Update dsn.sh 2017-10-12 19:34:04 -06:00
FusionPBX 91ecd0ce57 Update dsn.sh 2017-10-12 17:42:34 -06:00
FusionPBX 5145dc3266 Update config.sh 2017-10-12 17:30:19 -06:00
FusionPBX 712fb0bd0b Update fail2ban.sh 2017-10-09 11:35:04 -06: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 f585ca8216 Update pre-install.sh 2017-10-09 10:17:19 -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
FusionPBX 62feb25a5e Update source-release.sh 2017-10-07 12:11:26 -06:00
FusionPBX b6c8ea794c Update environment.sh 2017-10-07 11:53:05 -06:00
FusionPBX b7d2ac8352 Update environment.sh 2017-10-07 11:37:54 -06:00
FusionPBX dd3b6dcdf4 Update letsencrypt.sh 2017-10-07 11:24:08 -06:00
FusionPBX 4bfe46b13a Update reset_admin_password.sh 2017-10-07 11:19:07 -06:00
FusionPBX b11e744abe Update letsencrypt.sh 2017-10-07 11:17:24 -06:00
FusionPBX 64278a34fe Update fusionpbx.sh 2017-10-07 11:16:45 -06:00
FusionPBX f7715a70d6 Update fail2ban.sh 2017-10-07 11:16:04 -06:00
FusionPBX 59e1b5f58c Update finish.sh 2017-10-07 11:15:14 -06:00
FusionPBX 67ccb082cb Update environment.sh 2017-10-07 11:02:51 -06:00
TylerP 163929dd7c Update fusionpbx-maintenance.sh (#128)
I am a novice but I think I found some small items here to correct.  Most notably, the path for freeswitch voicemail is not proper, at least for my packages based install.
2017-09-16 13:31:35 -05:00
Len b7c24fe377 Update finish.sh (#124) 2017-09-07 15:33:16 -06:00
Len 04b7f748c4 Update finish.sh (#116)
* Update finish.sh

update class dates

* Update finish.sh

* Update finish.sh

* Update finish.sh
2017-09-06 21:45:59 -06:00
Mafoo d612f4c553 Enhance - report more on error in enviroment.sh (#99)
When there is a error with the enviroment report more information
fixes for the centos script that had some parts wrong
2017-09-02 09:10:37 -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