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

Private key protection of crypto tokens via explicit/manual login after server startup #21

Open
mbartosch opened this issue Sep 17, 2014 · 0 comments

Comments

@mbartosch
Copy link
Contributor

If the admin wishes to use software keys, it might not be desirable to keep the file unencrypted (or the passphrase in KeyNanny config).
For this case it might be interesting to supply the pass phrase after KeyNanny startup via the daemon protocol.
Of course, KeyNanny will not be able to serve requests for encrypted tuples before the private key has been unlocked.

Bonus points: consider secret sharing for key protection.

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

No branches or pull requests

1 participant