Consider brute-force protection on the Server-to-Server Sharing Endpoint
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
This is a little bit a trickier one, having brute-force protection there as well would be nice. However, the way S2S is implemented right now may lead to people locking out servers by intention.
Needs some more thoughts as well as status messages so that the other Nextcloud partiall throttles. Related to https://github.com/nextcloud/server/issues/437
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 reading the current Server-to-Server Sharing implementation and the related Nextcloud issue 437. Clarify how brute-force protection and status messages should work with partial throttling, including how to avoid intentionally locking out servers; done requires an agreed design and corresponding implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100