linux-kernel - Re: Security issues with local filesystem caching

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061026003202.GH29920@ftp.linux.org.uk>
Date:	Thu, 26 Oct 2006 01:32:02 +0100
From:	Al Viro <viro@....linux.org.uk>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	David Howells <dhowells@...hat.com>, sds@...ho.nsa.gov,
	jmorris@...ei.org, chrisw@...s-sol.org, selinux@...ho.nsa.gov,
	linux-kernel@...r.kernel.org, aviro@...hat.com
Subject: Re: Security issues with local filesystem caching

On Thu, Oct 26, 2006 at 12:37:39AM +0100, Alan Cox wrote:
> Ar Mer, 2006-10-25 am 11:14 +0100, ysgrifennodd David Howells:
> > Currently, CacheFiles temporarily changes fsuid and fsgid to 0 whilst doing its
> > own pathwalk through the cache and whilst creating files and directories in the
> > cache.  This allows it to deal with DAC security directly.  All the directories
> > it creates are given permissions mask 0700 and all files 0000.
> 
> That seems sensible and fine. It is precisely why we added a separate
> fsuid in the first place so that the user space nfsd could take on an fs
> identity without breaking signal and other security based forms.

I see a problem with that; not sure if that's what Christoph is objecting
to.  What about access to cache tree by root process that has nothing
to do with that daemon?  Should it get free access to that stuff, regardless
of what policy might say about access to cached files?  Or should we at
least try to make sure that we have the instances in cache no more permissive
than originals on NFS?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/