nextcloud / nextcloud/nextcloudpi
Allow users to extend the fail2ban configuration
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Whenever I configure fail2ban with "abuseIPDB" service ( https://www.abuseipdb.com ), the settings I added are always replaced by NCP fail2ban configuration.
It would be great that it could be possible to set the API key and the configuration of the service in the Fail2ban menu.
Unfortunately I'm not a developer for what I can only help with ideas and testing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Fail2ban menu and the NCP Fail2ban configuration that overwrites custom settings. Trace how the abuseIPDB service configuration is generated, including where an API key could be entered and preserved. Done means users can configure abuseIPDB through the Fail2ban menu without their settings being replaced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100