Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recovery: vulnerabilities and mitigations #32

Open
orthecreedence opened this issue Aug 10, 2022 · 0 comments
Open

Recovery: vulnerabilities and mitigations #32

orthecreedence opened this issue Aug 10, 2022 · 0 comments
Labels
discussion Needs discussion to become a feature project:core

Comments

@orthecreedence
Copy link
Member

Had a good discussion with a friend, and came to the conclusion that the recovery system (effectively multisig) is vulnerable. If an attacker can convince M of N recovery executors that attacker is you, then attacker can effectively gain control of the identity. Educating every executor (could be tech-illiterate friends, parents, or even lazy institutions) to perfectly verify the identity of the attacker each time could be mitigated through interfaces (ie, "Before signing this request, ask the recoveree a question only they would know the answer to") but this is still imperfect.

One main solution came to mind: like a revocation certificate, one would pre-generate a signed recovery request and store it securely. Generation of a new recovery request would require full access to the identity. This makes it impossible for an attacker to arbitrarily initiate recovery. And because recovery requires initial setup anyway, this doesn't add much more complication.

Another option is to embed the identity with recovery questions where the answers generate a private key that can be used to sign a recovery request. This alleviates the burden of storage of a separate pre-signed recovery request.

@orthecreedence orthecreedence added discussion Needs discussion to become a feature project:core labels Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Needs discussion to become a feature project:core
Projects
None yet
Development

No branches or pull requests

1 participant