-
Notifications
You must be signed in to change notification settings - Fork 997
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 modern stream ciphers like Chacha20 #317
Comments
@cayolblake Agreed, it will be better if we can support ChaCha20. Do you have bandwidth to work on this? |
I'm no Go developer but I can take a look if you give me some development level hints. Helped port Chacha20 support on a C++ project some years back and it was a real blast given the ending results. Is there some Slack/Discord where you guys hang to discuss such stuff? |
So I took a quick dig and could find It appears also only gold-standard Crypto is defined in the Go SDK where it gets used inside the project and introducing Chacha20 would required using external libraries. Is that how you do it guys? Am I going right on this or...? Also some Slack/Discord where discussions go would be really helpful tho. |
Yes, we used tons of external libraries.
Yes, the important thing would be keep it backward compatible.
We have a slack workspace, please find the invitation link in README |
What would you like to be added:
Support for modern/lightweight stream ciphers like Chacha20 beside current support of AES.
Why is this needed:
ChaCha20 takes a 256-bit key and a 32-bit nonce and then creates a key stream, which is then XORed with the plaintext stream. In software, it is three times faster than AES, and is well suited to lower-powered devices and in real time communications.
Quoted from -> https://medium.com/asecuritysite-when-bob-met-alice/aes-is-great-but-we-need-a-fall-back-meet-chacha-and-poly1305-76ee0ee61895
Also a nice coffee-time basic article https://blog.cloudflare.com/do-the-chacha-better-mobile-performance-with-cryptography/
The text was updated successfully, but these errors were encountered: