-
Notifications
You must be signed in to change notification settings - Fork 11
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
Node.js bindings #44
Comments
there is js bindings |
Yes, I saw them. But they're a transpilation to WA and JS, couldn't that introduce weaknesses to attacks that target the result of the transpilation? I mean, if the source of truth, the C code, is assumed to be safe, will that assumption still hold in the transpiled code? And what about performance? By Node.js bindings I mean native bindings/addons, so to use the C-compiled library directly from a Node.js app. |
all compilers are trying to optimize away things they shouldn't in the cryptographic context. even the c compilers :/
as much as in the compiled binary made from c i believe. wasm is really just a random architecture.
dunno about that. i guess it depends.
i see. would be nice to have, but having the wasm binding is good enough for me (especially since that also enables people to run this in their browsers). i have not planned a native binding, but if there is a contribution that is easy and pleasant to review, i might consider adding it. |
Given Node.js popularity for web backends, it could be beneficial to have bindings for it
The text was updated successfully, but these errors were encountered: