nextcloud / nextcloud/twofactor_gateway
Recovery keys
Open
Nobody has claimed this yet.
enhancement
gateway:signal
- Dominant language
- PHP
- Stars
- 122
- Forks
- 63
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 23
Description
This just crosses my mind:
- user has setup a signal gateway (not sure how the implementations are handling new keys)
- user is using 2F
- user gets a new phone, installs Signal, get's new keys
- want's to login into Nextcloud
- gateway refused to send due to security constraints (keys are not matching)
When enabling 2F like this, we should probably spit out some recovery keys like with TOTP (if I remember).
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
No files, tests, or entry points are named. Start by reviewing the existing two-factor authentication and gateway key-handling flow, then determine the recovery-key behavior and its test coverage before implementation. Done means recovery keys work safely when a user changes phones and gateway keys no longer match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100