Yes, and if you have a single user on the machine at a time (with cache flushed inbetween, kernel refreshed), root can read /dev/kmem, swap, intercept traffic and read cachefs data to its heart's content--hence, those requirements. -Dan -----Original Message----- From: Trond Myklebust [mailto:trond.myklebust@xxxxxxxxxx] Sent: Tuesday, December 30, 2008 2:36 PM To: Muntz, Daniel Cc: Andrew Morton; Stephen Rothwell; Bernd Schubert; nfsv4@xxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; steved@xxxxxxxxxx; dhowells@xxxxxxxxxx; linux-next@xxxxxxxxxxxxxxx; linux-fsdevel@xxxxxxxxxxxxxxx; rwheeler@xxxxxxxxxx Subject: RE: Pull request for FS-Cache, including NFS patches On Tue, 2008-12-30 at 14:15 -0800, Muntz, Daniel wrote: > >> As for security, look at what MIT had to do to prevent local disk > >> caching from breaking the security guarantees of AFS. > > > >See what David has added to the LSM code to provide the same > >guarantees > for cachefs... > > > >Trond > > Unless it (at least) leverages TPM, the issues I had in mind can't > really be addressed in code. One requirement is to prevent a local > root user from accessing fs information without appropriate permissions. > This leads to unwieldly requirements such as allowing only one user on > a machine at a time, blowing away the cache on logout, validating > (e.g., > refreshing) the kernel on each boot, etc. Sure, some applications > won't care, but you're also potentially opening holes that users may > not consider. You can't prevent a local root user from accessing cached data: that's true with or without cachefs. root can typically access the data using /dev/kmem, swap, intercepting tty traffic, spoofing user creds,... If root can't be trusted, then find another machine. The worry is rather that privileged daemons may be tricked into revealing said data to unprivileged users, or that unprivileged users may attempt to read data from files to which they have no rights using the cachefs itself. That is a problem that is addressable by means of LSM, and is what David has attempted to solve. Trond -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
