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

Extended PrivKey #5

Open
shayanb opened this issue Dec 20, 2014 · 0 comments
Open

Extended PrivKey #5

shayanb opened this issue Dec 20, 2014 · 0 comments
Labels

Comments

@shayanb
Copy link
Member

shayanb commented Dec 20, 2014

On the current coinos model, private keys are encrypted with the user's password and are saved in the same object (Hash Key: Hash Value) as the user.

db0/user/user:USERNAME

screen shot 2014-12-03 at 9 06 21 pm

But on our model, we should save them in another table, not accessible for the user. How should be the encryption?

Suggested method: We can use an RSA generated set of keys to encrypt all the private keys with the RSA public key and keep the RSA private key secure, and we will be able to decrypt the private keys from the SuperAdmin view on the browser using the RSA private key.
In this case even with the full access to the SuperAdmin user (user/password or hacks) it's not possible to get the private keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant