Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[crypto] next steps #59

Open
rt2zz opened this issue Mar 9, 2018 · 1 comment
Open

[crypto] next steps #59

rt2zz opened this issue Mar 9, 2018 · 1 comment

Comments

@rt2zz
Copy link
Member

rt2zz commented Mar 9, 2018

  1. check if cryptoVerify will work with strings (or if it requires a buffer)
  2. look into adding explicit serialize / rehydrate to cryptoCreateKeypair and cryptoSign
  3. write tests to cover all of this
@rt2zz
Copy link
Member Author

rt2zz commented Mar 9, 2018

one more reason not to go back to msgpack / buffers is that this will likely make compatibility more difficult with potential non-nodejs clients.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant