Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 1,569
    • Issues 1,569
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 32
    • Merge Requests 32
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #4090

Closed
Open
Opened Aug 10, 2016 by Jesse Norell@jnorell
  • Report abuse
  • New issue
Report abuse New issue

better fail2ban detection

feature request Under Monitor when displaying various log files, usually an empty log file just shows an empty output, but for fail2ban it incorrectly says fail2ban is not installed on this server. fail2ban.log does exist, and once it has contents it shows them, but after log file rotation on a not terribly busy/attacked server, the message is inaccurate and could be improved by actually testing for the presence of the software. (I suspect rkhunter could have the same issue?)

Assignee
Assign to
3.2
Milestone
3.2
Assign milestone
Time tracking
None
Due date
None
1
Labels
TODO
Assign labels
  • View project labels
Reference: ispconfig/ispconfig3#4090