Clear / refresh 2FA backup codes
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
as already mentioned in https://github.com/nextcloud/twofactor_totp/issues/244, maybe just a question...
but shouldn't the Backup-Codes be cleared/deleted after an user disables his 2FA?
in the database they are still present, also for users which were completely deleted ages ago.
i'm not sure if this may even become a security issue, especially if a user enables 2FA again...
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 reviewing the linked twofactor_totp issue and the database records described in this report. Determine the intended lifecycle for backup codes when 2FA is disabled, re-enabled, or a user is deleted; the issue is done only when that behavior and its security implications are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, databases, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100