5 ms·
Perhaps there are use cases where this would make sense (mobile?), but for a server-side application, wouldn't encrypting the filesystem be better? I'm just im
by cdoxsey 9y ago
Perhaps there are use cases where this would make sense (mobile?), but for a server-side application, wouldn't encrypting the filesystem be better?
I'm just imagining an operator trying to debug the system only to find out that he can't read any of the files from the terminal and will have to build custom programs using this library to operate with the data.
And it seems like there are API abstraction issues too... Imagine you use a library that writes some state to the file system using the standard lib. None of that data would end up encrypted because it didn't go through this library.
Whereas using the operating system's filesystem allows transparent compression and encryption without having to change your code at all.
- kazagistar 9y agoI could see it being used alongside Intel SGE for DRM or security reasons, in situations where the OS and system are considered hostile adversaries, but you still need extensive mutable external storage outside the application binary.