Lockout of the password exception across runs

Closed
  • Is something wrong?
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
56/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
security

Research direction

Read the password exception mentioned in the issue and trace how failed attempts are counted and how runs apply the account lockout policy. Add a way to count failures across runs so repeated runs cannot exceed that policy; done when attempts remain limited across runs. The issue names no files or tests, so locate the relevant code and checks in the repository.

Written by the indexing model from the issue text.

Description

roadmap

Count failed password attempts for the exception above the cap across runs, not only within one run, so a loop of runs cannot guess at the console faster than the account lockout policy allows.

Dominant language
Rust
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

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.

More from WikdSolvemProbler/process-tree-guard

All issues in WikdSolvemProbler/process-tree-guard

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.