[ON HOLD] wip: Reference implementation of message encryption #1127
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Work in progress implementation of message encryption - currently only working for Curve25519.
Details
Still to-do:
k256 = { version = "0.13.1", default-features = false, features= ["arithmetic", "ecdh", "alloc"], optional = true }
(although that might only support ECDH not static DH, so will need some investigation)Testing
More to come:
Update Recommendations
For dApp Developers
N/A
For Internal Integrators
Toolkit
When ready, can be used by the toolkit to implement message encryption as part of intent construction -- assuming OsRng is exposed the toolkit appropriately in the given runtime. (EG it might error in WASM unless a secure RNG is linked in, which depends on how the WASM is run).