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.

Sign up for GitHub

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

Jump to bottom

Don't store encrypted seed entropy #1486

Open
mnzaki opened this issue Oct 1, 2019 · 2 comments
Open

Don't store encrypted seed entropy #1486

mnzaki opened this issue Oct 1, 2019 · 2 comments
Labels
backlog

Comments

@mnzaki
Copy link
Contributor

mnzaki commented Oct 1, 2019

Description

Don't store the seed entropy, even if encrypted (password is in OS keystore). Instead store the derived key pairs directly. This will provide for added security (phone compromise is not necessarily a seed compromise any more). It will also make #1427 trivial

Current idea is to use the persona table to store the generated keys (encrypting the privateKey of course) and DID.
@mnzaki mnzaki added the backlog label Oct 1, 2019
@chunningham
Copy link
Contributor

@mnzaki this is something we should look at in the typeorm sdk storage stuff

@mnzaki
Copy link
Contributor Author

mnzaki commented Jun 3, 2020

Is this even in the notion backlog?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backlog
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mnzaki @chunningham