Feature request: configurable two/multi factor device / revocation
Open
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
In the event someone compromises a single device I have keybase on, that device can add new devices, or revoke all others, etc.
Some way of configuring the number of required devices to agree on certain operations would be ideal. The default configuration for existing users would be 1 - preserving current behaviour.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by tracing how devices are added and revoked, then determine where approval requirements could be configured. Done means operations can require agreement from a configurable number of devices while existing users retain the default of one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100