| |||||||||||||
CacheFS & SecurityCacheFS & SecurityPosted Sep 2, 2004 16:41 UTC (Thu) by scripter (subscriber, #2654)Parent article: A general caching filesystem
I wonder what the security implications of CacheFS are. Does each file inherit the permissions of the original? Is confidentiality a problem? What if you want to securely erase a file?
(Log in to post comments)
CacheFS & Security Posted Sep 3, 2004 19:49 UTC (Fri) by hppnq (guest, #14462) [Link] Not knowing anything about CacheFS internals, I would say these are cases of "don't do it, then". ;-)
CacheFS & Security Posted Sep 13, 2004 18:49 UTC (Mon) by AnswerGuy (guest, #1256) [Link] The only difference between accessing a filesystem directly and through CacheFS should be that the CacheFS can store copies of the accessed data on a local block device. In other words that there's a (potentially persistent) footprint of all accesses.
Other than that CacheFS should preserve the same permissions semantics as if a given user/host were accessing the backend filesystem/service directly.
|
|||||||||||||