message: return base64 for sign, make verify work with base64 string #230
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 is related to #217.
This returns a base64 signature for Message.sign, and allows verify to work with a base64 string (or a buffer). It's using the existing test suite and fixtures.
I'm more than a little confused about the standardization around base64 here, but it does seem to be the convention for everyone using it. Noteworthy is that we actually reduce test code because the fixture signatures are in base64.
We could also make a helper function (ala
signBase64
) instead, if we preferred to return a buffer here. But we should definitely provide an easy way for people to do this, since it seems to be common usage.