Change AES_GCM to aes-128-gcm#19
Merged
martinthomson merged 1 commit intoweb-push-libs:masterfrom Mar 30, 2016
Merged
Conversation
I am using an browserify version of node's crypto aes encryption, this is the only valid GCM cipher mode.
Member
|
Thanks, this is a recent change, I think. I really need to get around to updating my web crypto implementation some day. |
Contributor
Author
|
Could you please publish the new change to npm? Thank you very much! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I am using an browserify version of node's crypto aes encryption, this is the only valid GCM cipher mode. For normal nodejs, it should be similar to id-aes128-GCM.