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
I am trying to get a client-side encryption 🔐 library up and running that works both when Node is a client as well as when the browser is a client.
Unfortunately if I use browserify it will use crypto-browserify which quickly bloats my tiny library to render it cumbersome to load 🚂 (like 250k or so minified for the crypto require statement). I would like this to be faster 🚄 .
I can imagine one of three solutions for this:
Extend the Node.js's crypto API (send a PR) to be more modular in order to be able to decouple all the ciphers:
this way I would only need to bundle the ciphers that I need.
Have an "abstraction"-layer library that works pretty much like the API above except that its not in Node.js and that it falls back on the Node.js implementation. (Does this exist? 🤔 )
Use a crypto-subset library with a browser implementation. (Have they been tested? 💥 )
How do you approach crypto through npm on the browser?
What are good libraries?
Have there been approaches to make this better in the Node API?
The text was updated successfully, but these errors were encountered:
@karlpokus My client would like to have a symmetrically encrypted (where the key is not shared over the net; offline handshake) connection on top of https. It is for service accounts where they want to avoid man-in-the-middle attacks.
I am trying to get a client-side encryption 🔐 library up and running that works both when Node is a client as well as when the browser is a client.
Unfortunately if I use
browserify
it will usecrypto-browserify
which quickly bloats my tiny library to render it cumbersome to load 🚂 (like 250k or so minified for the cryptorequire
statement). I would like this to be faster 🚄 .I can imagine one of three solutions for this:
How do you approach crypto through npm on the browser?
What are good libraries?
Have there been approaches to make this better in the Node API?
The text was updated successfully, but these errors were encountered: