-
Notifications
You must be signed in to change notification settings - Fork 23
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
Support for X25519 key exchange and XChacha20 encryption #74
Comments
Thanks for the update. Don't worry, the configuration is optional |
Is the support for XChaCha20 planned? Fyi, there exists a statdard library for it ( |
The problem is that the new |
Indeed, I have found out that |
@L11r, honestly I don't really understand why the current solution shouldn't work with |
@pseusys your solution use |
@L11r, yes, that's exactly what I have wrutten in my PR: my solution solves one of the two problems named in this issue title. As far as I understood, they are mostly independant. |
@pseusys yes, sorry if I've sounded incorrect, you contribution is good! But I guess we need to merge and release complete solution and mark it as a new major version (e.g. v3). Let me see if something has been changed recently. |
@L11r, never mind, you didn't sound wrong! I just wanted to improve your library. |
@kigawas as far as I understand you are preparing this support for py/js/rs libraries. Currently Golang has new
crypto/ecdh
standard library, but it lacks of rich configuration, I could only add some basic support for x25519 and xchacha20, otherwise I would need to fork stdlib, which will require more maintance.The text was updated successfully, but these errors were encountered: