[GH-ISSUE #225] login brute force protection/fail2ban #179

Closed
opened 2026-02-26 09:36:32 +03:00 by kerem · 1 comment
Owner

Originally created by @yehudah on GitHub (Mar 14, 2017).
Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/225

Hello,

Great product !

Is there a way to protect the login/auth page from abuse ? stuff like fail2ban for example.

Thanks

Originally created by @yehudah on GitHub (Mar 14, 2017). Original GitHub issue: https://github.com/opensolutions/ViMbAdmin/issues/225 Hello, Great product ! Is there a way to protect the login/auth page from abuse ? stuff like fail2ban for example. Thanks
kerem closed this issue 2026-02-26 09:36:32 +03:00
Author
Owner

@boppy commented on GitHub (May 27, 2017):

Mine is writing a log at ./var/log/vimbadmin.log:

# FAILED AUTH:
2017-05-27T13:09:04+02:00 NOTICE (5) [178.0.0.0]: Authentication failure for admin@example.com

# SUCCESSFUL AUTH:
2017-05-27T13:03:52+02:00 INFO (6) [178.0.0.0]: admin@example.com logged in

Just adopt the settings from a running fail2ban filter (at /etc/fail2ban/filter.d on a debian).

<!-- gh-comment-id:304446110 --> @boppy commented on GitHub (May 27, 2017): Mine is writing a log at `./var/log/vimbadmin.log`: ``` # FAILED AUTH: 2017-05-27T13:09:04+02:00 NOTICE (5) [178.0.0.0]: Authentication failure for admin@example.com # SUCCESSFUL AUTH: 2017-05-27T13:03:52+02:00 INFO (6) [178.0.0.0]: admin@example.com logged in ``` Just adopt the settings from a running fail2ban filter (at `/etc/fail2ban/filter.d` on a debian).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ViMbAdmin-opensolutions#179
No description provided.