nextcloud / nextcloud/bruteforcesettings

Some more control and visibility

Open
#4 10 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement overview
Dominant language
JavaScript
Stars
55
Forks
18
Avg merge
9h 28m
Merged PRs (30d)
21

Description

Some ideas:

  • IP blacklist (...also showing IPs that are currently blocked with a countdown)
  • Edit the time an IP is blocked
  • Edit the attempts a user can do without being blocked

...very eccentric wishes would be 😜

  • make it possible to disable brute-force protection at all? [implemented; see config.php.sample / Admin Manual]
  • define those settings per group/user

What do you think? @rullzer @LukasReschke

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing config.php.sample and the Admin Manual, which document the already-implemented option. The remaining requests are broad and cover IP blacklisting, block timing, attempt limits, and per-user or per-group settings; choose one scope and define its behavior before identifying what would count as done.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authentication, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.