Add sign/verify support #124
Merged
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.
Two methods were added to the JSEncrypt class:
sign, which takes a string to sign, a hash method, as well as the name of the hash methodverify, which takes a string to verify, its signature, and a hash methodThe name of the hash method is required because RSA signatures need a header depending on which hash was used (see https://tools.ietf.org/html/rfc3447#page-43).
I tested that generated signatures can be verified by JSEncrypt, jsrsasign, and SubtleCrypto with no issues. It can verify signatures from JSEncrypt, jsrsasign, and SubtleCrypto also.
Fixes issue #2.
Signing example
Verifying example