Use WebCryptoAPI for encryptAes and decryptAes (Prototype) #75
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
Open
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.
Hi,
the company I'm working for, needed a demo application using OTR and the WebCryptoAPI. Therefore I modified the version v0.2.12 of otr.js to use the WebCryptoAPI instead of CryptoJS for AES encryption.
As the WebCryptoAPI is completely asynchronous, it does not really fit the current design which relies on synchronous call. But you will see that quite fast if you review the code.
Maybe you have some use for it.
Best Regards,
Oliver
Spec of WebCryptoAPI: http://www.w3.org/TR/WebCryptoAPI/