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

Ability to specify secret key when creating a hyperdb #158

Closed
aral opened this Issue Jan 24, 2019 · 4 comments

Comments

Projects
None yet
1 participant
@aral
Copy link
Contributor

aral commented Jan 24, 2019

In hypercore, you can specify secretKey in the options object passed to the constructor.

This allows you to, for example, generate the keys from a Diceware passphrase.

In order to support the same use case, you should be able to do the same with hyperdb.

@aral

This comment has been minimized.

Copy link
Contributor Author

aral commented Jan 24, 2019

See discussion.

@aral

This comment has been minimized.

Copy link
Contributor Author

aral commented Jan 24, 2019

To clarify, you can specify the secret key and other options when creating the initial hyperdb instance and they are used (it’s the hypercore created afterwards that you have no control over currently)

@aral

This comment has been minimized.

Copy link
Contributor Author

aral commented Jan 24, 2019

Related: #137

@aral

This comment has been minimized.

Copy link
Contributor Author

aral commented Feb 1, 2019

Closing this as you can pass the secret key in the options and what I ended up exploring in the PR mentioned above is actually not necessary for creating a seamless device/node authorisation process for multiwriter.

@aral aral closed this Feb 1, 2019

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