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
Wouldn't it be better do encrypt/decrypt data in the application layer, when before and after getter/setter, using libraries that are good for encryption?
I think it is better to keep these two things isolated, also do lower the amount of dependencies in the library.
There are no additional dependencies and a built-in wrapper (while not the javascript way of rewriting everything under the sun) would be helpful.
Granted, I guess I could just write a module that wraps this one to do the same thing but, given that it can use the built-in crypto library, it seems reasonable as a native feature.
As a user, I would like the ability to selectively encrypt my filesystem cache.
I'd be happy to help with implementation on this if you are open to the idea.
The text was updated successfully, but these errors were encountered: