Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

consistent whitelist/blacklist managing #93

Open
JMLX42 opened this issue Nov 5, 2016 · 1 comment
Open

consistent whitelist/blacklist managing #93

JMLX42 opened this issue Nov 5, 2016 · 1 comment

Comments

@JMLX42
Copy link
Owner

JMLX42 commented Nov 5, 2016

The CMS makes it easy to add/remove whitelisted/blacklisted IPs.
The blacklist/whitelist are managed through iptables.
Other apps, such as fail2ban, will also interact with iptables.

We must make sure that the CMS is always up to date with the iptables rules.
We must also make sure that /etc/fail2ban/jail.conf (especially ignoreip is always up to date with the CMS content).

@JMLX42
Copy link
Owner Author

JMLX42 commented Nov 6, 2016

A possible solution for the blacklist would be to have a custom fail2ban action that would call a new /api/scripts/blacklist-ip.js script.

Reference: http://askubuntu.com/questions/435511/fail2ban-creating-a-custom-action-that-gives-parameters-to-script

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant