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

Storage of Private Key Data? #1

Open
Kefkius opened this issue Sep 10, 2015 · 0 comments
Open

Storage of Private Key Data? #1

Kefkius opened this issue Sep 10, 2015 · 0 comments

Comments

@Kefkius
Copy link
Member

Kefkius commented Sep 10, 2015

Eventually, a tool will exist that can make use of private keys. (Transaction Builder really already fits this criterion, as it could have the ability to sign transactions.)

The question of how to deal with private keys presents itself. Since Hashmal is intended to help developers, it makes sense that someone who knows what they're doing should be unencumbered by measures designed to protect less-experienced users.

Nevertheless, I think it's unwise to go beyond storing private keys in RAM (e.g. writing them in the config file). Doing so would require something like:

  1. Creating a system of optional key encryption, in which encrypted keys are stored and the user must do something to decrypt them when they're needed.
  2. Something else?

Is there a feasible use-case (e.g. tool) in which permanent storage of private key data is necessary?

And if so, is there a better way to save private key data than the option listed above?

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

No branches or pull requests

1 participant