feat: x25519 shared secret #731
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boorad
force-pushed
the
feat/x25519-shared-secret
branch
from
2587014 to
d623b1e
Compare
renanmav
reviewed
Jul 24, 2025
boorad
force-pushed
the
feat/x25519-shared-secret
branch
from
eefb078 to
0c2683b
Compare
boorad
force-pushed
the
feat/x25519-shared-secret
branch
from
c205c48 to
5e89da9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
crypto.generateKeyPair()andcrypto.generateKeyPairSync()real things like the implementation guide says they arex25519andx448crypto.diffieHellman()for Node APIEd.getSharedSecret()for Noble Curves APIexpo-pluginexpo-build-propertiesfromdevDependenciestodependenciesas it is directly imported.