-
Notifications
You must be signed in to change notification settings - Fork 53
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
Consider supporting CAESAR recommendations #306
Comments
Thanks for the suggestion. I agree that new AEAD algorithms are needed. OCB is also a CFRG recommendation (and specified in RFC7253), so I agree it could make sense as an option.
I'll try to find out whether there's implementor interest for this :) |
Here's a draft spec for AES-OCB in Web Crypto: https://twiss.github.io/webcrypto-modern-algos/#aes-ocb. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The CAESAR competition for standardizing new AEAD algorithms wrapped up a while ago and some new very fast constructions were recommended (see, https://competitions.cr.yp.to/caesar-submissions.html). For benchmarks, see eBACS.
Most of these recommendations (especially the recommendations for use case 2) take advantage of AES-NI instructions already widely available in hardware. There's also no more patents on AES-OCB iirc.
Is there any interest in bringing these algorithms to the browser?
The text was updated successfully, but these errors were encountered: