-
Notifications
You must be signed in to change notification settings - Fork 4
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
JS Key Chain #6
Comments
Is this going to adhere to what was already done for the golang implementation? |
@RangerMauve Yes, the Also need |
@RangerMauve Encrypted PubSub is easy with CMS. Simply convert the topic message (plain message) into CMS (cipher message) and then publish. The CMS message contains the information needed (the key id) to convert the cipher message into a plain message. |
So the goal is to get IPFS to seamlessly integrate with rfc5652 messages for every level of the API? |
@RangerMauve Yes, that is the goal. See the keystore spec for suggested API changes. |
Thanks to a short discussion with @diasdavid, a few things have been clarified
The key store is some implementation of interface-datastore. Note: 16 minutes of discussion equates to 5 hours of refactoring! |
@richardschneider Could you maybe link to the discussion if there's a digital version available? |
@RangerMauve The source is now available at https://github.com/libp2p/js-libp2p-keychain |
Implement a key store #2 in JavaScript. See the doc, code and spec
It must
It could
The text was updated successfully, but these errors were encountered: