We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey, I was wondering if you're willing to accept a merge request to allow using XC20P as a content-encryption algorithm. It is still not part of the latest JWE RFC specs, but according to this - https://www.rfc-editor.org/rfc/rfc8439.html - and this - https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-xchacha-01 - it is already something that is becoming widely accepted.
Also, the golang x/crypto already has an implementation for the XChaCha algorithm, so the changes shouldn't be too impactful.
x/crypto
Thanks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hey, I was wondering if you're willing to accept a merge request to allow using XC20P as a content-encryption algorithm. It is still not part of the latest JWE RFC specs, but according to this - https://www.rfc-editor.org/rfc/rfc8439.html - and this - https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-xchacha-01 - it is already something that is becoming widely accepted.
Also, the golang
x/crypto
already has an implementation for the XChaCha algorithm, so the changes shouldn't be too impactful.Thanks
The text was updated successfully, but these errors were encountered: