POC Encrypt/Decrypt expense title on client side

[ChristopherJohnston]

Proof of concept outlining SHA-256 encrypt/decrypt of expense title on the client using libp2p/keychain and libp2p/cms, storing the private key in IndexedDb using datastore-idb

NB the encrypt/decrypt calls are quite slow so probably not a practical solution!

[vercel]

@ChristopherJohnston is attempting to deploy a commit to the Sebastien Castiel Team on Vercel.

A member of the Team first needs to authorize it.

[ankitbahl]

This looks like RSA (Public key crypto) - For basic encryption, a symmetric key encryption methodology should be used. For example AES. This will likely speed up those calls (Symmetric key cryptography is generally much faster)

Doesn't JS already have build in crypto functionality? Not sure how performant it is comparatively.

[ChristopherJohnston]

It's using CMS, which utilises an RSA private key for encryption. This particular proof of concept makes use of libp2p/cryptography which stores the keys in an IndexedDB within the browser's local storage.

The slowness I'm now attributing to the time it's taking for the UI graph to rebuild rather than the individual encrypt/decrypt calls.

That said, I have no real preference to which encryption method is used - this really was an exercise to see if it could be done without significant changes.

[ChristopherJohnston]

closing this for now as it's more of a proof of concept - will revisit at a later date