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
There is no technical limitation AFAIK, AES-GCM-256 would work fine on the IEEE-754 float64 data format used by JavaScript to store numbers (I did this a while back for another project, source), with proper padding (float64 is 64 bits, so we'd need a constant 64 bits of padding for a 128 bit AES block size).
The main challenge in implementing this (and/or other data types) is how to define the data format that is being encrypted: how to go from a JavaScript variable to an array of bytes to encrypt, and on decryption how to go back from the decrypted array of bytes back into a JavaScript data type.
For SQL-based schemas, I suppose we could use the schema metadata to know what kind of processing to do, but I'm not sure how that would translate in MongoDB / NoSQL schemas.
Hey folks,
I recently started using this for a hobby project and noticed that it is possible to encrypt Strings only.
Is there some inherent plugin/cryptography limitation to encrypting numbers, or was this just never a priority to implement?
If someone could give me a couple of hints around this I'd love to take a stab at implementing support for it.
The text was updated successfully, but these errors were encountered: