You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The branch on which PR #48 is located, used the browser dom web crypto API to get going (in order to make the task more manageable). Node JS uses the same Web Crypto API but somewhat differently, and so it seems better to build a local facade as is done for the symmetric keys.
Implementing more cryptographic algorithms, such as in #51, would help lay the groundwork of tests to help work out what parts of the facade need to be written.
The text was updated successfully, but these errors were encountered:
Node JS uses the same Web Crypto API but somewhat differently
Minor clarification: Node.js has its own crypto APIs. Also, in recent versions they've experimentally provided the Web Crypto API as well, but so far there are no stability guarantees for it.
The branch on which PR #48 is located, used the browser dom web crypto API to get going (in order to make the task more manageable). Node JS uses the same Web Crypto API but somewhat differently, and so it seems better to build a local facade as is done for the symmetric keys.
Implementing #52 will likely depend on this.
Implementing more cryptographic algorithms, such as in #51, would help lay the groundwork of tests to help work out what parts of the facade need to be written.
The text was updated successfully, but these errors were encountered: