keybase / keybase/keybase-issues
require multi-device approval to revoke a device
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Right now, each device signed into one keybase account is a single point of failure. If an attacker gains control of an active and unlocked device, they can revoke all other devices on the account, and all is lost.
What if revocation could require confirmation by more than one device?
Maybe a user-configurable setting for minimum number of devices that must agree to revoke another?
Props to https://keybase.io/jab416171 for the initial suggestion.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. First clarify the scope and acceptance criteria for configurable multi-device approval, including what counts as a successful revocation.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100