(feat) add support for aes-256-gcm algo for JWE #44
Conversation
This file contains 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
|
@cdbattags - can you please review this PR ? |
|
Hi @vinayakhulawale! Haven't forgotten about this. Tests look great. Should have this merged by tomorrow morning. |
|
@cdbattags - ping :) |
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.
This PR adds support for aes256gcm encryption algo for content encryption.
Also replaces uses for
resty.aeswith functions fromlua-resty-opensslas former one will not be updated anymore to add new algos.We can also replace
evp.luain future PRs with functions fromlua-resty-opensslcc: @cdbattags