MarcelGarus / MarcelGarus/murderers
Implement login attempt throttling
Open
Nobody has claimed this yet.
[P] Major
[T] Backend
[T] Frontend
- Dominant language
- Dart
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In order to make the authentication more save according to [Mobile App Authentication Architectures](https://sushi2k.gitbooks.io/the-owasp-mobile-security-testing-guide/content/0x04e-Testing-Authentication-and-Session-Management.html), throttle the login attempts after several failed ones.
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 application's login and authentication entry points, then read the linked mobile authentication guidance for the relevant throttling considerations. Done means repeated failed login attempts are throttled after the chosen threshold, with the behavior verified in the relevant authentication flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100